Skip to main content
Glama

Get one case

get_case
Read-onlyIdempotent

One case by its reference (for example BF-7K2M9Q): what the notice says, the verdict, and where the appeal stands. Needs the account's API key or sign-in.

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": {
      "ref": "<ref>"
    },
    "name": "get_case"
  }
}

Input Schema

NameRequiredDescriptionDefault
refYesThe case reference, e.g. BF-7K2M9Q.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/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 safety is covered. The description adds real value beyond them by stating the authentication requirement (API key or sign-in), which no annotation expresses. It stops short of error behavior for an unknown reference, keeping it from a 5.

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 tight sentences: the identity of the tool first, then the returned contents, then the prerequisite. No filler, no repetition of the title, and the example is placed inline rather than padding a separate 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?

With no output schema and one required parameter, this description does the heavy lifting well: it previews what the response contains and flags the auth need. Only the not-found/error path is unaddressed, a minor gap for a simple read tool.

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 coverage is 100% and the single `ref` parameter is fully documented in the schema, including the same BF-7K2M9Q example. The description's mention of the reference adds nothing the schema does not already carry, so the baseline 3 applies.

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?

"One case by its reference" gives a specific verb-equivalent (retrieve a single case), the resource (case), and the lookup key (reference), and the singular framing separates it from the list/search siblings. The clause naming what comes back (notice, verdict, appeal status) tells an agent exactly what question this tool answers before 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 Guidelines3/5

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

Usage is implied rather than stated: needing a single case reference points at this tool, and the auth note hints at a prerequisite. But it never says when to prefer this over list_cases or search, nor what happens if the agent only has partial information.

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.