Skip to main content
Glama

get_mcp_schema

Read-onlyIdempotent

Discover patch keys, read includes, and per-kind configuration fields for MCP tools. Omit module to list all modules; pass module and optional kind (block_kind, question type, or flow entity kind) for field-level detail.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_mcp_schema"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNoblock_kind, question type, or flow entity kind when module is block, question, or flow
moduleNoMCP surface area to describe

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is fully covered. The description adds useful behavioral detail about output granularity — module omitted yields a module list, module plus kind yields field-level detail. It does not mention size, caching, or that results are static reference data; with an output schema present, explaining returns is unnecessary, so a 3 is fair.

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?

Two sentences, no filler. The object of the tool comes first and the omit/pass branching is front-loaded as the second sentence.

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 2-optional-parameter read-only introspection tool with a full output schema and complete annotation coverage, the description supplies everything needed to call it correctly. The only shortfall is that it doesn't situate itself against sibling read_* tools when an agent is choosing between discovery and direct reads.

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%, so the baseline is 3, but the description earns an extra point by explaining the conditional semantics: 'module' omitted means list all, and 'kind' is only meaningful when module is block, question, or flow. That is a dependency between parameters the schema cannot express.

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?

The description names a specific action ('Discover') and concrete resources ('patch keys, read includes, and per-kind configuration fields for MCP tools'), which is far more specific than a generic 'get schema'. It does not explicitly contrast itself with the read_*/edit_* siblings, but the schema-discovery framing is distinctive enough for an agent to distinguish it.

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?

It gives explicit branching instructions: omit module to list all modules, or pass module with an optional kind for field-level detail. This tells the agent how to get two different levels of results. It lacks an explicit statement of when this tool is preferable to reading a resource directly (e.g. read_block vs block schema), which keeps it below a 5.

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