MCP Tools

​

Creating a Tool

1. Open the Create Modal: Click the “Create” button in the app sidebar or press ‘C’.
2. Select “Tool”: In the modal, choose the “Tool” option.
3. Name Your Tool: Enter a descriptive name (e.g., “Get Weather Forecast”, “Search Products”) and click “Create”.

​

Configuring Tool Basics

• Name: The display name shown in the UI.
• Slug: A unique identifier used internally (auto-generated from the name).
• Description: Clearly explain what the tool does. This helps the LLM understand its purpose (e.g., “Fetches the current weather for a given city”).

​

Defining Tool Inputs (Parameters)

• Example: A weather tool needs a location parameter. A product search tool might need a query parameter.

1. Navigate to the “Parameters” section.
2. Click “Add Parameter”.
3. Configure each parameter:
   • Name: Give it a short, descriptive name using only letters, numbers, and underscores (e.g., location, search_query, user_id).
   • Type: Choose the data type the LLM should provide:
     • string: For text (e.g., a city name, a search term).
     • number: For numerical values (e.g., an item ID, a quantity).
     • boolean: For true/false values.
   • Required: Check this box if the LLM must have this information to run the tool.
   • Description: Explain what this specific piece of information is for (e.g., “The city and state for the weather forecast”). This helps the LLM ask the right clarifying questions if needed.

​

Defining Tool Steps (API Requests)

1. Add a Step: In the flow builder area, click the “Add Step” button (look for the + icon).
2. Configure the Step: Select the step to open its configuration panel.
   • Step Name: A label for the step (e.g., “Fetch Forecast Data”).
   • Method: Choose the HTTP method required by the API (e.g., GET, POST).
   • URL: Enter the API endpoint URL.
     • Using Parameters in URLs: To insert a parameter value into the URL, use double curly braces and the param. prefix: https://api.weather.com/forecast?city={{param.location}}.
     • Using Environment Variables: You can also securely insert sensitive values (like API keys stored elsewhere) using the env. prefix: https://api.service.com/data?apiKey={{env.SERVICE_API_KEY}}. (Environment variables are configured on the tools page).

​

Configuring Step Details (Auth, Headers, Body)

• Authentication:
  • Select the authentication method the API uses (e.g., Bearer Token, Basic Auth).
  • Enter the required credentials. You can use {{param...}} and {{env...}} placeholders here (e.g., {{env.MY_API_KEY}} for a Bearer Token).
• Headers & Query Parameters:
  • Add any required HTTP headers (e.g., Content-Type, Accept) or additional URL query parameters.
  • Values can use {{param...}} and {{env...}} placeholders.
• Request Body (for POST, PUT, etc.):
  • Body Type: Choose the format the API expects (e.g., JSON, Form Data).
  • JSON Body Configuration:
    • Write the JSON structure the API needs.
    • Use {{param...}} and {{env...}} placeholders for dynamic values.
    • Placeholder Quoting is Crucial:
      • If inserting a string parameter, wrap the placeholder in double quotes: "message": "{{param.user_message}}"
      • If inserting a number or boolean parameter, do not use quotes: "itemId": {{param.product_id}}, "notify": {{param.send_notification}}
    • Complex JSON: If the API needs nested objects or arrays, build the structure directly in the JSON editor. Use placeholders only for the individual primitive values (string, number, boolean) provided by your parameters.
      • Example: Sending a structured message
        Copy

        {
          "notification": {
            "title": "{{param.message_title}}",
            "retries": 3,
            "recipient": {
              "id": "{{param.recipient_id}}"
            }
          }
        }
        

        (Here, message_title and recipient_id would be defined as string parameters).

​

Conditional Logic in JSON Bodies (Advanced)

• Use Case: Include an optional discountCode field only if the discount_code parameter was supplied, and an optionalNumber field only if optional_number was supplied.

{
  "requiredField": "{{param.some_value}}",
  "discountCode": {
    "_if": {
      "present": [
        "toolInput.discount_code"
      ],
      "then": "{{param.discount_code}}"
    }
  },
  "optionalNumber": {
    "_if": {
      "present": [
        "toolInput.optional_number"
      ],
      "then": {{param.optional_number}}
    }
  }
}

• The entire field (e.g., discountCode, optionalNumber) will only be included in the final JSON sent to the API if the conditions within its _if block are met.
• _if: This special key indicates conditional logic for the parent field.
• present: An array containing one or more strings. Each string must be the name of a tool input parameter (prefixed with toolInput.) that must be present (i.e., provided by the LLM) for the condition to be true. All parameters listed must be present.
• then: Specifies the value to assign to the parent field (e.g., discountCode) if the present condition is met. Remember to use the correct placeholder syntax ({{param...}}) and quoting: Wrap string placeholders in double quotes ("{{param...}}") and leave number/boolean placeholders unquoted ({{param...}}).

​

Working with Multiple Steps (Advanced)

• Adding More Steps: Simply add more steps to the flow builder.
• Using Previous Step Data: In a later step’s configuration (URL, Headers, Body, etc.), you can reference data from a previous step’s output using {{steps[INDEX].body.fieldName}} or {{steps[INDEX].headers.headerName}}. INDEX is the 0-based number of the previous step (e.g., {{steps[0].body.userId}} uses the userId field from the body of the first step (index 0)). The last step’s output is automatically considered the final result of the tool.

​

Saving Changes