Test2
asdf
0.1.0
Test2 provides a streamlined toolkit for developers to create and manage events, orders, users, applications, and documents through a set of versatile API tools. This toolkit simplifies the integration process, allowing for efficient handling of complex data structures without requiring authentication.
Capabilities
- Create and manage calendar events with detailed attendee and location information.
- Handle orders with dynamic pricing and various payment methods.
- Create user profiles with comprehensive data and preferences.
- Submit applications across multiple domains with required and optional documentation.
- Update existing documents with flexible operations.
No authentication or secrets are required to utilize this toolkit, enabling straightforward implementation in various applications.
Available tools(6)
| Tool name | Description | Secrets | |
|---|---|---|---|
Create a calendar event with attendees and location.
NOTE: If you have not already called get_body_scheme('create_event') or are unsure
about the body structure, call it first to see the exact schema required.
The body should include title, startTime, attendees, and location
(oneOf: physical/virtual/hybrid). Optionally include recurrence and reminders. | |||
Create a new order with items and payment information.
NOTE: If you have not already called get_body_scheme('create_order') or are unsure
about the body structure, call it first to see the exact schema required.
The body should include customerId, items with complex pricing (anyOf: fixed/discounted/tiered),
payment method (oneOf: credit_card/paypal/bank_transfer), and shipping information. | |||
Create a new user with complex profile information.
NOTE: If you have not already called get_body_scheme('create_user') or are unsure
about the body structure, call it first to see the exact schema required.
The body should include email, profile with contact method (oneOf: phone/email/social),
optional address, and preferences. | |||
Get the OpenAPI schema for a tool's request body.
This function returns the complete OpenAPI specification for the body parameter
of the specified tool, with all references resolved. Use this to understand
the exact structure required before calling any of the API tools.
Available tools:
- create_user
- create_order
- create_event
- update_document
- submit_application | |||
Submit an application (job, visa, loan, or university).
NOTE: If you have not already called get_body_scheme('submit_application') or are unsure
about the body structure, call it first to see the exact schema required.
The body should include applicationType, personalInfo with identification
(oneOf: passport/drivers_license/ssn), documents array, and additionalInfo
(anyOf based on application type). | |||
Update a document with multiple operations.
NOTE: If you have not already called get_body_scheme('update_document') or are unsure
about the body structure, call it first to see the exact schema required.
The body should include documentId and an array of operations
(anyOf: insert/delete/replace/format). Each operation type has different required fields. |
Selected tools
No tools selected.
Click "Show all tools" to add tools.
Requirements
Select tools to see requirements
Test2.CreateEvent
Create a calendar event with attendees and location. NOTE: If you have not already called get_body_scheme('create_event') or are unsure about the body structure, call it first to see the exact schema required. The body should include title, startTime, attendees, and location (oneOf: physical/virtual/hybrid). Optionally include recurrence and reminders.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
body | string | Required | JSON string containing event data. If unsure about structure, call get_body_scheme('create_event') first. |
Requirements
Output
json— No description provided.Test2.CreateOrder
Create a new order with items and payment information. NOTE: If you have not already called get_body_scheme('create_order') or are unsure about the body structure, call it first to see the exact schema required. The body should include customerId, items with complex pricing (anyOf: fixed/discounted/tiered), payment method (oneOf: credit_card/paypal/bank_transfer), and shipping information.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
body | string | Required | JSON string containing order data. If unsure about structure, call get_body_scheme('create_order') first. |
api_version | string | Required | API version to use |
idempotency_key | string | Required | Unique key to prevent duplicate orders |
Requirements
Output
json— No description provided.Test2.CreateUser
Create a new user with complex profile information. NOTE: If you have not already called get_body_scheme('create_user') or are unsure about the body structure, call it first to see the exact schema required. The body should include email, profile with contact method (oneOf: phone/email/social), optional address, and preferences.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
body | string | Required | JSON string containing user data. If unsure about structure, call get_body_scheme('create_user') first. |
tenant_id | string | Required | The tenant/organization identifier |
source | string | Optional | Source system or application creating the user |
Requirements
Output
json— No description provided.Test2.GetBodyScheme
Get the OpenAPI schema for a tool's request body. This function returns the complete OpenAPI specification for the body parameter of the specified tool, with all references resolved. Use this to understand the exact structure required before calling any of the API tools. Available tools: - create_user - create_order - create_event - update_document - submit_application
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
tool_name | string | Required | The name of the tool to get the body schema for |
Requirements
Output
json— No description provided.Test2.SubmitApplication
Submit an application (job, visa, loan, or university). NOTE: If you have not already called get_body_scheme('submit_application') or are unsure about the body structure, call it first to see the exact schema required. The body should include applicationType, personalInfo with identification (oneOf: passport/drivers_license/ssn), documents array, and additionalInfo (anyOf based on application type).
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
body | string | Required | JSON string containing application data. If unsure about structure, call get_body_scheme('submit_application') first. |
priority | string | Required | Processing priority level |
notification_email | string | Required | Email for status notifications |
Requirements
Output
json— No description provided.Test2.UpdateDocument
Update a document with multiple operations. NOTE: If you have not already called get_body_scheme('update_document') or are unsure about the body structure, call it first to see the exact schema required. The body should include documentId and an array of operations (anyOf: insert/delete/replace/format). Each operation type has different required fields.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
body | string | Required | JSON string containing document update operations. If unsure about structure, call get_body_scheme('update_document') first. |
workspace_id | string | Required | The workspace containing the document |
user_id | string | Required | User performing the update |
track_changes | boolean | Optional | Whether to track changes |
Requirements
Output
json— No description provided.