Skip to main content
Glama

Pandex

Outline of a law

get_outline
Read-onlyIdempotent

The structure of a document: its parts, chapters and articles with their headings and element ids. Use it to find the right article of a long law before reading it.

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": {
      "id": "<id>"
    },
    "name": "get_outline"
  }
}

Input Schema

NameRequiredDescriptionDefault
atNoThe structure as it stood on this day, YYYY-MM-DD.
idYesAn id from a result, or an identifier or citation.
langNoTwo-letter language, for texts that exist in several.
underNoOnly the structure below this element (a part or chapter).
max_tokensNoSize of the answer in tokens, 200–8000. Default 1500.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/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 safety profile is covered. The description usefully discloses the shape of what comes back (parts, chapters, articles, headings, element ids), which annotations cannot. It does not warn that output can be truncated by max_tokens or how at/lang/under affect the response.

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 short sentences, front-loaded with what is returned and followed by the operative use case. No filler, no restatement of the title.

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?

No output schema exists, so the description carries the burden of describing the return value, which it does at a useful level of detail (hierarchy levels plus headings and ids). What is missing is minor: truncation behavior from max_tokens and the temporal/versioning effect of the 'at' parameter.

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 description coverage is 100%, so every parameter (at, id, lang, under, max_tokens) is already documented with format hints. The description says nothing beyond the schema about how those arguments shape the result, so it neither compensates nor detracts; 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 concrete resource and its payload: 'the structure of a document: its parts, chapters and articles with their headings and element ids.' An agent immediately knows this is a structural outline retrieval, distinct from a full-text read. It stops short of explicitly naming the sibling it complements (get_document), relying on 'before reading it' to imply the split.

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 a clear situational cue: 'Use it to find the right article of a long law before reading it,' which tells the agent this is a navigation step preceding a document read. No explicit exclusion or precondition (e.g., when a full read is preferred, or behavior when the document is short) is stated.

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