Skip to main content
Glama

Cases citing this case

get_citing_cases
Read-onlyIdempotent

Full citator list: every ranked case citing this one, with judge-written parentheticals (usable verbatim in a brief), verbatim quotes, pin cites, and the citing court's own Bluebook signal. Filter by flag color. Best for FINDING SUPPORTING AUTHORITY and parentheticals; for comprehensive negative-treatment checking use get_treatment (this list covers only each case's top-ranked ~50 citers).

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

Input Schema

NameRequiredDescriptionDefault
citationNoReporter citation (used if cluster_id absent)
case_nameNoCase name; lets a citation newer than the reporter index resolve by name + date (candidates returned if several share the name)
cluster_idNoCluster id of the case
max_citersNoDefault 25, max 100
flag_filterNoComma list of flag colors to include: red,yellow,green,neutral,procedural. Omit for all.
forum_stateNoOptional two-letter state code of the court you file in (il, ga, tx ... dc). Adds forum_cite to every case: the citation in the form that state's courts use for their own reports (other cases in Bluebook form), pinned where cite_as is.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / forum_state
      Added value: +{
      +  "description": "Optional two-letter state code of the court you file in (il, ga, tx ... dc). Adds forum_cite to every case: the citation in the form that state's courts use for their own reports (other cases in Bluebook form), pinned where cite_as is.",
      +  "type": "string"
      +}
  2. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuinely new behavioral context beyond them: the ranked ordering, the ~50-citer coverage ceiling, and the fact that parentheticals are usable verbatim. It stops short of pagination or rate-limit behavior, which keeps 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, front-loaded with purpose, then the exclusion/routing clause in second position. The return-field enumeration (parentheticals, quotes, pin cites, signals) is dense but earns its place given there is no output schema. Minor cost: the first sentence is heavily comma-laden and could parse faster.

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

Completeness5/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 correctly compensates by describing what comes back (parentheticals, verbatim quotes, pin cites, court signals, forum_cite). It also discloses the coverage limitation that could otherwise mislead an agent into thinking the list is exhaustive, which is the single most important caveat for a citator 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 description coverage is 100%, so every one of the six parameters (including forum_state's detailed forum_cite semantics) is already fully documented in the schema. The description only glosses 'Filter by flag color', repeating flag_filter's purpose, and does not touch max_citers or forum_state, so it adds marginal meaning over the schema. 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?

The description opens with a specific verb and resource ('Full citator list: every ranked case citing this one') and enumerates what makes the list useful (parentheticals, quotes, pin cites, Bluebook signal). It immediately distinguishes itself from get_treatment by naming that sibling as the tool for comprehensive negative-treatment checking.

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

Usage Guidelines5/5

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

Explicit when-to-use ('Best for FINDING SUPPORTING AUTHORITY and parentheticals') and explicit when-not ('for comprehensive negative-treatment checking use get_treatment'), paired with the reason to switch (this list covers only top-ranked ~50 citers). This is exactly the routing guidance an agent needs between two closely related citator tools.

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