Skip to main content
Glama

create_tool

Create a custom HTTP tool for APIs that are not registered native integrations. Use when a playbook needs a reusable HTTP call. Auth header values should use "{{SECRET_NAME}}" placeholders from create_secret. Registered vendors must use metaphor.integration in step code instead (see list_integrations). Authoring details are in get_builder_guide topic "tool".

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "id": "<id>",
      "name": "<name>",
      "description": "<description>",
      "execute": "<execute>"
    },
    "name": "create_tool"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesKebab-case identifier, e.g. "slack-notify"
nameYes
executeYes
descriptionYes
inputSchemaNoInput JSON Schema
outputSchemaNoOutput JSON Schema

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.2/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=false, openWorldHint=true and destructiveHint=false, so the write-and-external nature is known. The description adds non-obvious operational context beyond that: auth header values must use '{{SECRET_NAME}}' placeholders sourced from create_secret, which is a security-relevant constraint. It stops short of stating whether the id must be unique, what happens on duplicate ids, or what is returned.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four short sentences, front-loaded with the purpose, then the trigger, then the exclusion, then the pointer to deeper docs. Each sentence carries distinct information with no filler; the only mild cost is that the last two are reference-style pointers rather than self-contained guidance.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with nested objects, four required parameters, no output schema and only 50% schema coverage, the description covers routing and secret handling well but omits the shape of the 'execute' block and the roles of 'inputSchema'/'outputSchema'. Pointing at get_builder_guide partially compensates, leaving an agent dependent on a second call to author confidently.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 50%, so the schema documents only part of the six parameters (id format, auth modes, header placeholders) while 'name', 'description', 'execute.url' and 'method' remain bare. The description reinforces the secret-placeholder convention for headers but adds no meaning for the undeclared fields, and it defers the rest to an external guide. Adequate but leaving real semantic gaps for a nested-object tool.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Create a custom HTTP tool') plus the scope that makes it distinct: APIs that are not registered native integrations. It also distinguishes itself from the native-integration path by naming 'metaphor.integration' and 'list_integrations', so an agent can route correctly without opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit trigger ('Use when a playbook needs a reusable HTTP call') and an explicit exclusion ('Registered vendors must use metaphor.integration in step code instead (see list_integrations)'). It also routes the agent to 'get_builder_guide' topic 'tool' for authoring details, covering both when and where-else.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources