Skip to main content
Glama

Secure Autonomous Register

Get a case

get_case
Read-onlyIdempotent

The full case: every claim with its type (fact, assertion, interpretation) and source links, the outcome, controls that failed, were absent or held, the Register's labeled interpretation, right-of-reply status for each named party, corrections, and a ready citation.

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_case"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe case ID, such as REG-0011. search_cases returns the IDs.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / id / description
      Previous value: -"Case ID such as REG-0011"New value: +"The case ID, such as REG-0011. search_cases returns the IDs."
  2. First observed

TDQS

A3.5/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 needs no restating. The description adds genuine substance beyond that by disclosing the depth of the payload, including source links, right-of-reply status and the Register's labeled interpretation, but it says nothing about pagination, size limits, or what happens when a case is not found.

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?

One front-loaded sentence that leads with 'The full case' and then lists components; every clause adds a distinct field rather than repeating structured data. It is dense but readable, with mild cost from being a long unbroken enumeration without an explicit verb.

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 output schema, the description does the work of describing the return shape, which is appropriate for a single-ID read tool and makes the definition largely self-sufficient. Gaps remain around error behavior and whether the payload is truncated for large cases.

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 single id parameter is already documented with its format (REG-0011) and its origin (search_cases returns the IDs). The description adds nothing about parameters, which is acceptable at this coverage level and near the baseline for a one-parameter tool.

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 opens with 'The full case' and then enumerates exactly what that entails (claims with types and source links, outcome, control status, labeled interpretation, right-of-reply status, corrections, citation), so an agent knows precisely what it gets back and how it differs from a summary-level tool. It lacks an explicit retrieval verb and never names a sibling, so differentiation from search_cases is only implied via the schema note that search_cases returns IDs.

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

Usage Guidelines3/5

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

There is no explicit when-to-use or when-not-to-use statement; usage is only implied by the 'full case' framing versus a lighter-weight sibling like search_cases. The workflow hint (search_cases returns the IDs, feed one in) lives in the schema parameter description rather than the tool description, leaving guidance implicit.

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