Skip to main content
Glama

Inputs, price and example of one tool

describe_tool
Read-onlyIdempotent

Everything needed to call one tool: what it does, every input with its type, whether it is required and an example value, the price per successful call (and the lower price with a prepaid key where there is one), whether it is in the free calls, an example call and the shape of its answer. Free. Take the name from find_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": {
      "name": "<name>"
    },
    "name": "describe_tool"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesThe tool's name from find_tool, for example weather_forecast

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, destructiveHint false, openWorldHint false), so the bar is lower. The description still adds genuinely new context beyond them: the call is free, prices are per successful call, and a cheaper prepaid-key rate may exist and is disclosed — cost behavior an agent could not infer from the schema or annotations.

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?

One dense sentence front-loads the payload list, then a short tagline and the routing instruction. It is long but each clause names a distinct returned field; only the parenthetical on prepaid pricing is slightly wordy.

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?

Critically, there is no output schema, and the description compensates by promising an example call and the shape of the answer, plus pricing and free-call status. It does not say what happens when the name is unknown or disallowed, which is the main remaining gap for a single-param lookup tool.

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?

There is a single parameter at 100% schema description coverage, and the schema already says it is the tool name from find_tool with a weather_forecast example. The description repeats that guidance without adding format, length, or error semantics, so it sits at the baseline where the schema does the work.

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 description names a concrete verb and resource — it returns everything needed to call one tool: inputs with types and required flags, price, free-call status, example call, answer shape. It also distinguishes itself from find_tool by making find_tool the source of the name rather than a substitute, so an agent can tell the two apart 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 Guidelines4/5

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

Explicit prerequisite and workflow: "Take the name from find_tool," which tells the agent the sequencing (find first, then describe). It does not state when to skip this tool in favour of call_tool or price_token, so the exclusion side is only implied by the content listing.

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.