Skip to main content
Glama

Describe tools

describe_tools
Read-onlyIdempotent

The full definitions of tools you name — description and input schema — from the hub's complete tool set, of which this door lists only a part. Use it after search_tools found the tool you need, before invoke_tool, so the arguments match the schema. Read-only, no account, nothing is called. Returns one definition per name, and says which names are unknown.

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": {
      "names": "<names>"
    },
    "name": "describe_tools"
  }
}

Input Schema

NameRequiredDescriptionDefault
namesYesTool names as search_tools returned them

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / names / description
      Added value: +"Tool names as search_tools returned them"
  2. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent and non-destructive, and the description partially restates that. It nevertheless adds context the annotations cannot express: no account is required, nothing is actually invoked, and unknown names are reported back rather than silently dropped. It doesn't discuss output shape beyond the one-definition-per-name promise, but nothing important is missing.

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?

Two sentences, front-loaded with what is returned, then the when-to-use ordering, then the guarantees. The parenthetical 'of which this door lists only a part' is slightly convoluted but earns its place by scoping the result set.

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

Completeness5/5

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

With no output schema and a single required parameter, the description carries the full burden and does so: it says what comes back (one definition per name), how failures are surfaced (unknown names reported), and that no account or invocation occurs. Nothing an agent needs before calling is absent.

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 schema's own description already tells the caller to pass names 'as search_tools returned them'. The prose adds no new constraint on the names array — the useful detail here is about the return value, not the parameter, so the baseline of 3 applies.

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: returns 'the full definitions of tools you name — description and input schema' from the hub's complete set. The clause 'of which this door lists only a part' explicitly separates it from search_tools, so an agent can tell the two apart without opening either 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 workflow position — 'after search_tools found the tool you need, before invoke_tool' — plus the reason ('so the arguments match the schema'). Both the alternative and the selecting condition are named, leaving nothing to inference.

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.