Skip to main content
Glama

Run a tool by name

call_tool
Read-only

Run one of this service's tools by name. Costs that tool's own price per successful call (most $0.01; describe_tool and find_tool show it); a failed call costs nothing, and tools marked inFreeCalls run free while the caller has free calls left. Pass the tool's inputs as "arguments". If you do not know the name or the inputs, call find_tool or describe_tool first: a wrong name or a missing input is refused before anything is charged. A tool that costs more than $0.10 a call (find_tool marks it needsMaxPrice) runs only when you pass that price as "max_price"; without it the call is refused, uncharged, and the refusal states the price.

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
nameYesThe tool's name from find_tool, for example weather_forecast
argumentsNoThe tool's inputs as an object, for example {"city": "Paris"}. See describe_tool for a tool's inputs
max_priceNoOnly for a tool that costs more than $0.10 a call: the most this call may cost, for example "$1.00". Leave it out for every other tool

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.7/5.0
Behavior5/5

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

Annotations only declare readOnly/openWorld/non-destructive/non-idempotent; the description adds the pricing model (cost per successful call, most $0.01, free failures, inFreeCalls free-tier behavior) and the pre-charge validation guarantee for wrong names and missing inputs. These are exactly the operational traits annotations cannot express.

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?

Front-loaded with purpose, then pricing, then the discovery prerequisites, then the max_price rule — a logical order with no filler. The sentences are long and multi-clause, which costs some readability, but every clause carries actionable information.

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 dispatcher with three params, no output schema, and a nested arguments object, the description covers selection, cost, validation, and the price gate thoroughly. The one gap is return behavior: it never says the call yields the target tool's result, which an agent needs to know when consuming output.

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%, so baseline is 3, but the description adds real meaning: arguments is the wrapped tool's input object (deferring to describe_tool for shape) and max_price is a conditional gate tied to the needsMaxPrice marker in find_tool rather than a general budget field. The enforcement consequence of omitting max_price is stated, which goes beyond the schema text.

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?

Opens with a specific verb+resource: run one of this service's tools by name, i.e. a generic dispatcher. It immediately contrasts itself with the discovery siblings find_tool and describe_tool, so an agent can distinguish it from 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?

Explicit routing guidance: if you don't know the name or inputs, call find_tool or describe_tool first; if a tool is marked needsMaxPrice, pass max_price or the call is refused. It also states the refusal is uncharged and states the price, which tells the agent what to do next on failure.

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.