Skip to main content
Glama

Describe a tool's arguments

describe_tool
Read-only

Returns the full description and JSON Schema of any Swissyphus tool so you can call it correctly. Use it to inspect required parameters before running call_tool.

Instructions

Full description and JSON Schema of the arguments of any Swissyphus tool this server exposes, for use with call_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
nameYesTool name, e.g. 'query_dataset'

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.3

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=true, openWorldHint=true), so the description's job is to say what comes back, and it does: a full description plus JSON Schema of the arguments. That is genuinely useful given there is no output schema. It omits failure behavior for invalid or non-existent tool names, which keeps it from a 5.

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 sentence, front-loaded with the return value and ending with the intended companion tool. Every clause carries information, though the phrasing ('of the arguments of any ... tool this server exposes') is slightly nested and could be tightened.

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 one-parameter meta-tool with no output schema this is close to sufficient: the agent knows what it gets back and how it relates to call_tool. Missing only edge-case behavior (unknown names, whether disabled tools are included), which is a modest gap for such a simple 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?

Schema coverage is 100% and the single 'name' parameter already carries an example ('query_dataset'). The description adds only the notion that the name refers to a tool this server exposes, which is minor clarification over the schema. Baseline 3 applies since the schema does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (describe) and resource (arguments of a tool), plus exactly what is returned: the full description and JSON Schema. Scope is bounded to 'any Swissyphus tool this server exposes', which tells an agent it works generically rather than on one fixed tool. It does not explicitly distinguish itself from discovery siblings like find_tools, but the pairing with call_tool does most of that work.

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

Usage Guidelines3/5

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

'for use with call_tool' implies the intended two-step workflow: describe first, then invoke. However, it never says what to do when the tool name is unknown (e.g., use find_tools first) or that it should be skipped when the schema is already known. Usage is implied rather than spelled out.

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

Deploy Server

Other Tools