Tool actions define what operation the AI agent can perform using the API.Documentation Index
Fetch the complete documentation index at: https://docs.sigmamind.ai/llms.txt
Use this file to discover all available pages before exploring further.

Steps:
- Click on Add New Tool
- Enter the following details:
| Field | Description |
|---|---|
| Action Name | Name of the action (e.g., Reschedule Booking) |
| Description(Optional) | What the action does |
| Endpoint URL | API endpoint URL |
| Request Method | GET, POST, PUT, DELETE |
| Headers | Required headers from API documentation |
| Body | Request payload |

Tool Name
Definition:A unique identifier for the tool action. The agent uses this name internally to trigger the correct API call. Requirements:
- Must be unique
- Use snake_case format
- No spaces allowed
Description (Optional)
Definition:Explains when and why the agent should use this action. This helps the AI understand the correct context for calling the API. Example:
HTTP / Request Method
Definition:Specifies the type of operation to perform on the API. Supported methods:
- GET → Retrieve data
- POST → Create data
- PUT → Update data
- PATCH → Partially update data
- DELETE → Remove data
Endpoint URL
Definition:The API endpoint where the request will be sent. You can use input variables to dynamically insert values. Static example:
{{booking_id}} will be dynamically provided by the agent.
Headers
Definition:Headers provide additional information required by the API, such as authentication and content type. Common headers example:
| Key | Value |
|---|---|
| Content-Type | application/json |
| Authorization | Bearer access_token |
Query Parameters
Definition:Query parameters allow you to filter or modify the API response. These are appended to the endpoint URL. Example configuration:
| Key | Value |
|---|---|
| status | booking_status |
Request Body
Definition:The request body contains the data sent to the API when creating or updating resources. You can use input variables to dynamically pass values.

Input Variables (Dynamic Placeholders)
Input variables are dynamic placeholders written inside double curly braces. Format:- User input
- Conversation context
- Extracted variables configured in the agent workflow
- Agent configuration
- Endpoint URL
- Query Parameters
- Request Body
Complete Example: Reschedule Booking (Cal .com)
Action NameHow Input Variables Work
Conversation Example:
User: I want to reschedule my appointment for tomorrow at 10 AM.What SigmaMind AI does:
- Extracts values from conversation
- Maps values to variables
- Replaces variables in the API body
- Calls the API automatically
Final API Request Sent:
- Click Submit Action
You can add new actions to an existing integration in the App Marketplace in the same way, allowing your AI agent to perform additional operations using the connected app.
How to Test Tool
You can test a tool action to verify that the API works correctly before using it in your agent.
Steps:
- Go to Tool Library from the Agent Builder
- Select the tool (for example, Cal.com)
- In the Tools section, locate the tool you want to test
- Click the Test button next to the action
- Enter test values for the detected input variables (such as
{{start_date}},{{end_date}},{{event_type_id}}) - Click Run Test
- Review the response to confirm the API is working correctly

Step 5: Use the Custom Tool in the Agent
After creating and testing your tool actions, you must add them to your agent. This allows the agent to call the tool during conversations and perform real-world operations. Method 1: Go to your Tools section- Find your tool (like
get_available_slots) - Click Add to Agent
- Fill the Description
- Bind placeholders (if required)
- Then click Add to Agent
Method 2:
- Open the Agent Builder
- Click Add Tool
- Click Add Integration Tool
- Select the app you created or configured
- Select the tool you want the agent to use
- Click Add to Agent

2. Using the API
If you prefer programmatic control, use the Integration Tools API to create a tool.Field descriptions
| Field | Required | Description |
|---|---|---|
| name | required | Unique name for the tool within this integration (e.g. get-customer) |
| description | required | Natural language description of what the tool does — agents use this to decide when to invoke it |
| method | required | HTTP method: GET, POST, PATCH, PUT, or DELETE |
| url | required | Full endpoint URL the tool will call (e.g. https://api.stripe.com/v1/customers/{id}) |
| queryParams | optional | Array of query parameter definitions — each with key, value, and description |
| bodyParams | optional | Object describing the request body schema — used for POST / PATCH / PUT requests |
| headers | optional | Array of custom headers to include with every call from this tool, each with key and value |
Add New Tool
- User: I want to reschedule my appointment
- Agent collects the required information
- Agent calls Reschedule Booking action
- API processes the request
- Agent confirms the reschedule
Best Practices
- Always follow the API documentation of the external app
- Use clear variable names
- Test actions before enabling
- Configure authentication properly
- Use descriptive action names