Skip to main content
Glama

Invoke tool

invoke_tool

Call any of the hub's tools by name with its arguments — the way to reach tools this door does not list (found with search_tools, defined by describe_tools). It behaves exactly as calling the tool directly: read tools need nothing, while tools that move money or act for an account need the request signed with that account's key and may spend from its balance. Returns that tool's own result, or its refusal with the reason.

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": {
      "name": "<name>"
    },
    "name": "invoke_tool"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesThe tool to call, by the name search_tools gave
argumentsNoIts arguments, shaped as the input schema describe_tools returned

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / arguments / description
      Added value: +"Its arguments, shaped as the input schema describe_tools returned"
    • addedInput schema / properties / name / description
      Added value: +"The tool to call, by the name search_tools gave"
  2. Added

TDQS

A4.8/5.0
Behavior5/5

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

Beyond the annotations (openWorldHint true, destructive false), the description discloses that behavior is identical to a direct call, that read tools need no auth, and that tools moving money or acting for an account require a signed request from that account's key and may draw on its balance. It also covers the response contract: the target tool's own result or its refusal with a reason. Nothing here contradicts destructiveHint=false — the proxy itself does not destroy state, the callee might.

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?

Three sentences, each carrying distinct information, with the core purpose front-loaded before the routing detail and the auth/cost caveat. Dense but well ordered; a slightly more scannable split of the auth clause would improve it marginally.

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

Completeness5/5

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

For a generic proxy with a nested free-form arguments object and no output schema, the description supplies everything an agent needs: how to discover the target, how to shape arguments, what authorization and cost the callee may impose, and what comes back on success or refusal.

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

Parameters4/5

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

Schema coverage is 100% and both parameters are documented, so baseline is 3. The description earns above baseline by tying each parameter to its source: name comes from search_tools and arguments must match the input schema describe_tools returned, which explains the required discovery workflow before invocation.

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?

The definition opens with a specific verb and resource ("Call any of the hub's tools by name with its arguments") and immediately scopes it to tools this endpoint does not list. It names search_tools and describe_tools as the discovery/preparation path, so an agent can distinguish this proxy from the sibling discovery tools without opening any 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?

It states exactly when to use it: for tools not exposed on this door, found via search_tools and defined via describe_tools. It also gives the when-not implication — for tools the door does list, the direct call is equivalent and available. Alternatives and the selection condition are both explicit.

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.