Skip to main content
Glama

Whizbrew

See how to use tools

describe_tools
Read-only

The full input schema, output type, price and one example call for 1 to 10 tool names from search_tools. Free.

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, e.g. ["tiktok.profile"]

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

The annotations already declare readOnlyHint=true, destructiveHint=false and closed-world, so safety is covered; the description adds cost behavior ("Free") and enumerates the payload, both of which matter in a catalog that also contains add_money, get_balance and get_quote. It does not say what happens when a supplied name is unknown or invalid, which is the main remaining behavioral gap.

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?

A single front-loaded sentence that enumerates the returned artifacts and then the input bound and provenance, with no filler. Every clause carries information.

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?

With no output schema, the description compensates by naming the four returned artifacts (input schema, output type, price, example) and stating the cost. Complete for a lookup tool, minus edge-case behavior for unresolvable names.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the names array already carries minItems/maxItems and an example, so the schema does most of the work (baseline 3). The description nonetheless adds provenance semantics not in the schema — the names must come from search_tools — which meaningfully constrains valid input.

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 retrieval action (full input schema, output type, price, one example call) for a specific resource (tool names), and explicitly ties the resource to search_tools, which distinguishes it from the search sibling. An agent knows exactly what comes back 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?

"for 1 to 10 tool names from search_tools" establishes the prerequisite step and the input bound, which is real workflow guidance. It stops short of explicit exclusions (e.g. don't call before searching, don't use for cost comparison alone), so it is clear context rather than full when/when-not routing.

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