Skip to main content
Glama

Get an Indiana case cluster

case_get
Read-onlyIdempotent

One Indiana opinion cluster by CourtListener cluster id. Includes opinion text only when the extract has a body. Includes author when that index is loaded: the slip byline, not the trial judge and not a holding. version_signal is a caution (yellow / red / year banner), never a green certified mark.

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": {
      "cluster_id": "<cluster_id>"
    },
    "name": "case_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
cluster_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, and non-destructive, so the safety profile is covered; the description adds genuine behavioral context beyond that — opinion text is present only when the extract has a body, author is present only when that index is loaded. The caveats about version_signal being a caution banner and never a certified mark are exactly the kind of nuance annotations cannot express.

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?

Four short sentences, front-loaded with the resource and key, with no filler. The phrasing is telegraphic in places ("when that index is loaded") and the final sentence about version_signal arrives without setup, which costs a little clarity but not length.

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?

Output schema exists, so return values need not be spelled out, and the annotations cover the safety profile. What is missing is the operational glue: how to get a cluster_id, and what happens on an unknown id — gaps that matter for a lookup tool whose only parameter is an opaque identifier.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With schema description coverage at 0% and one required parameter, the description carries the full burden, and it does only partially: it identifies the domain as "CourtListener cluster id" but gives no format, example, or pointer to how an agent obtains one. Naming the id namespace is the minimum, not a substitute for real parameter semantics.

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 verb (get), resource (one Indiana opinion cluster), and lookup key (CourtListener cluster id), so an agent can tell it retrieves a single record rather than searching. It does not name or differentiate itself from any sibling such as case_search, which is presumably how a cluster_id is obtained, so the sibling differentiation element of a 5 is absent.

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?

"One ... cluster by CourtListener cluster id" implicitly conveys that this is the by-id retrieval path, distinct from a search tool, but the description never says when to use it versus case_search or the citation-resolution siblings. There are no explicit exclusions, prerequisites, or instructions on where a cluster_id comes from, leaving usage to inference.

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.