Skip to main content
Glama

Describe a flayr tool

describe_tool
Read-onlyIdempotent

[read-only] Returns one tool's full description and input schema. Some listed tools are shortened to save tokens: they end with "Full description and schema: describe_tool". Every argument in the full schema is accepted.

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 name, e.g. "publish".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the "[read-only]" prefix is redundant. The description does add real context about the truncation convention in listings and states that every argument in the full schema is accepted, which helps the follow-up call. It says nothing about error behavior for an unknown name or the shape of what is returned.

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?

Three short sentences, front-loaded with the read-only tag and the core verb. The bracketed read-only marker duplicates the annotation, but there is otherwise no padding.

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 discovery tool with no output schema, the description covers what it returns, when to use it, and that the returned schema is authoritative for arguments. Only the response structure and unknown-name behavior are unstated, which are minor gaps.

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 is documented with an example in the schema itself. The description adds no format, casing, or lookup rules beyond the schema, so the baseline 3 applies.

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 and resource: returns one tool's full description and input schema. That is distinct from call_tool or search_tools by implication, though no sibling is named. An agent can tell what it retrieves without opening the 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?

Gives an explicit trigger condition: tools whose entries end with "Full description and schema: describe_tool" are truncated and should be expanded here. It does not explicitly contrast with search_tools or say this should precede call_tool, but the when-to-use context is clear.

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