Skip to main content
Glama

call_tool

Executes an already-active tool by name when a client’s tool list has not refreshed after activation. It runs registered tools only and does not activate inactive ones.

Instructions

Execute an already-active tool by name. Use this when activate_tools/activate_domain registered a tool but your client did not refresh its tool list. Does not auto-activate inactive tools.

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": "call_tool"
  }
}

Input Schema

NameRequiredDescriptionDefault
argsNoArguments object to pass to the tool
nameYesThe tool name to execute (from search_tools or describe_tool results)
argumentsNoAnother alternative: MCP clients that stringify the entire arguments wrapper. Carries the same nested {name, args/parameters} payload as a JSON string.
parametersNoAlternative: JSON-serialized arguments string. Some MCP clients serialize the nested arguments as a single stringified-JSON field.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.3.1
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • addedInput schema / properties / arguments
      Added value: +{
      +  "description": "Another alternative: MCP clients that stringify the entire arguments wrapper. Carries the same nested {name, args/parameters} payload as a JSON string.",
      +  "type": "string"
      +}
    • addedInput schema / properties / parameters
      Added value: +{
      +  "description": "Alternative: JSON-serialized arguments string. Some MCP clients serialize the nested arguments as a single stringified-JSON field.",
      +  "type": "string"
      +}
  2. First observedv0.3.0

TDQS

A4.4/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full behavioral burden; it does disclose the important non-activation constraint, which is real added context. However it says nothing about what happens when the named tool is inactive or unknown (error vs no-op), whether execution has side effects, or how results are returned. For a generic proxy-executor this leaves meaningful behavioral gaps.

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

Conciseness5/5

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

Two short sentences, zero filler, with the core action first and the usage constraint second. Nothing could be removed without losing a distinct fact.

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

Completeness4/5

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

For a no-output-schema proxy tool with rich schema documentation, the description covers the purpose, the trigger, and the key limitation. It stops short of describing failure behavior for inactive tools, which is the main remaining unknown an agent needs before calling.

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 description coverage is 100%, so the schema already defines all four parameters including the stringified alternatives, making the baseline 3. The description adds a useful selection hint by saying execution is "by name" and referencing where names come from in search_tools/describe_tool results, though it never discusses the args/arguments/parameters alternatives itself.

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 ("Execute an already-active tool by name") and immediately bounds the scope to already-active tools. An agent can distinguish it from activate_tools/activate_domain, which register tools rather than run them, 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?

Gives an explicit trigger condition (a tool was registered but the client did not refresh its tool list) and an explicit exclusion ("Does not auto-activate inactive tools"), which is exactly the precondition failure an agent would otherwise hit. It also implicitly routes activation needs to activate_tools/activate_domain.

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