Skip to main content
Glama

Last Price

call_tool

Destructive

Run any Last Price tool by name, including one this connection does not list. Find the name and its arguments with search_tools first. What it does, and whether it changes anything, is what that tool says.

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 to run, e.g. "list_webhooks".
argumentsNoThe arguments for that tool, as its input schema from search_tools describes. Defaults to {}.

Output Schema

NameRequiredDescriptionDefault
messageNoA short sentence about the result that an agent can show its person.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedOutput schema / properties / message / description
      Added value: +"A short sentence about the result that an agent can show its person."
  2. Added

TDQS

A4.2/5.0
Behavior4/5

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

The description adds real context beyond the annotations: the invoked tool may be one this connection does not expose, and effects are whatever the target tool declares rather than the conservative destructiveHint=true on the dispatcher itself. It stops short of describing failure behavior for an unknown name or whether the target's output is passed through unchanged.

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?

Three short sentences, front-loaded with what the tool does, then the naming prerequisite, then the behavior caveat. Nothing is padded or repeated.

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 dynamic dispatcher with arbitrary nested arguments this covers the essentials: how to obtain the name, how to shape arguments, and that semantics belong to the target tool; an output schema exists so return values need no explanation. The remaining gap is error handling for an unresolvable tool name.

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 100% and both properties are self-documenting, so the baseline is 3. The description reinforces where the name and argument shape come from (search_tools), but adds no detail beyond what the schema's "as its input schema from search_tools describes" already conveys.

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?

"Run any Last Price tool by name, including one this connection does not list" gives a specific verb (run) and resource (a named tool), plus the non-obvious scope that unlisted tools are reachable. It also implicitly separates this from the sibling search_tools, which only finds names.

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

Usage Guidelines4/5

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

"Find the name and its arguments with search_tools first" is an explicit prerequisite that routes the agent to the sibling before calling. It does not say when to call a listed tool directly instead of going through this dispatcher, so the boundary against the other siblings is only implied.

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