Skip to main content
Glama

describe_schema

Read-onlyIdempotent

Returns node and relationship counts plus direction conventions for the operations graph, helping agents understand its structure before querying.

Instructions

Node and relationship counts and the direction conventions of the graph.

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": "describe_schema"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, and an output schema exists to document return values. The description adds only a sketch of the returned content (counts and direction conventions), saying nothing about cost, freshness, scope of the graph, or whether counts cover the whole store or a filtered subset.

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?

A single short sentence with no wasted wording. However, it is a sentence fragment lacking a verb (e.g., 'Returns node and relationship counts...'), which slightly weakens front-loaded action framing.

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

Completeness3/5

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

With no parameters, full annotation coverage, and an output schema, the bar is low and the description mostly clears it. Still, for a tool named describe_schema it leaves unclear whether schema structure (labels, relationship types, properties) is included alongside counts, which is the exact ambiguity an agent needs resolved.

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?

The tool takes zero parameters, so the baseline is 4; there is nothing for the description to disambiguate. It correctly implies a parameterless overview call, though it never explicitly states that no arguments are accepted.

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

Purpose3/5

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

The description names concrete returned content (node and relationship counts, direction conventions), which is more specific than a tautology, but it is a noun fragment with no verb and sits at odds with the name describe_schema, which suggests schema/structure description rather than graph statistics. An agent cannot confidently tell whether this returns counts, schema definitions, or both.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no prerequisites, and no mention of alternatives such as read_only_cypher or reconciliation_report. The agent must infer that this is an orientation/overview call rather than a data-query call.

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