Skip to main content
Glama

Read a case

get_case
Read-onlyIdempotent

Fetch one case: metadata, parallel citations, treatment flag, and full opinion text (paginated via offset/max_chars). cited_by is the number of opinions citing the case: CourtListener's count, or the syfert.com citation graph's when that finds more (cited_by_source: citation_graph says so); for a decision filed as several twin clusters it is summed over them (cited_by_note says so), and a duplicate or stub twin id is answered with its survivor (note says so). Citations inside the returned text are checked against the reporter index (embedded_citations); citation_warnings names any the court itself got wrong. Identify the case by cluster_id (from search_cases results) or by reporter citation. find_text returns passages: up to 5 sentence-bounded windows holding a phrase (or its closest match) with star_page and offset, so a long opinion need not be paged (pass include_text=false to get only those); quotable=true adds quotable_passages, the passages of this opinion other courts quote. Quotation marks mean pasted from a tool result (opinion text, passage, best_match). If you typed a quote from memory, run verify_quote and use best_match. Run check_brief on the finished draft and apply its corrections. Copy cite_as for the citation (first page, then pin). A California Court of Appeal opinion with a Supreme Court docket event carries citability {status depublished | review_granted | transferred | review_decided, date, s_number, source, rule Cal. R. Ct. 8.1115}; depublished / review granted / transferred lead with status_warning (a depublished opinion may not be cited; one under review has no binding effect, is citable for persuasive value and to establish a conflict in authority, and the cite must note the grant; one transferred with directions to vacate is generally not citable; order_says quotes the order when held); old_rule true = review granted before 2016-07-01, when the grant itself depublished the opinion (a later decision did not restore it): may_cite no, check the docket. focus = a question or proposition in plain words (no brief sentence needed): returns focus_passages, the 4 (focus_n, at most 8) passages of about 2,000 characters that bear on it most, each with page, offset, lexical score and part (majority / concurrence / dissent / syllabus ...), instead of reading from the opening; opinion text is then left out unless include_text=true. focus_miss=true means no passage matched (nothing else is returned). With pin, the first passage is the pinned page's own best window.

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

Input Schema

NameRequiredDescriptionDefault
pinNoWith focus: the page you cite ("1250" or "1250-51"); the first focus passage is then that page's best window (source: pin) and the ranked passages follow
focusNoA question or proposition in plain words, e.g. "whether a FOIA fee waiver requires a public-interest showing": returns focus_passages (placed by word overlap, ranked; the rest of the opinion is not returned)
offsetNoCharacter offset for paging long opinions (use next_offset from a prior call)
focus_nNoWith focus: passages to return (default 4, at most 8)
citationNoReporter citation, e.g. "819 So. 2d 732" (used if cluster_id absent)
quotableNoWith include_text, also return quotable_passages: the passages of this opinion other courts quote, with star_page
case_nameNoCase name; used only when the citation is not in the reporter index (newer than it): resolves by name + decision-date window and returns candidates if several cases share the name
find_textNoA phrase to locate in the opinion: returns passages (exact, or the closest match) with star_page and offset
max_charsNoMax characters of opinion text to return (default 40000, max 150000)
cluster_idNoCluster id from search results
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.
include_textNoInclude opinion text (default true)

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. Changed1 schema field changed
    • addedInput schema / properties / pin
      Added value: +{
      +  "description": "With focus: the page you cite (\"1250\" or \"1250-51\"); the first focus passage is then that page's best window (source: pin) and the ranked passages follow",
      +  "type": "string"
      +}
  3. Changed2 schema fields changed
    • addedInput schema / properties / focus
      Added value: +{
      +  "description": "A question or proposition in plain words, e.g. \"whether a FOIA fee waiver requires a public-interest showing\": returns focus_passages (placed by word overlap, ranked; the rest of the opinion is not returned)",
      +  "type": "string"
      +}
    • addedInput schema / properties / focus_n
      Added value: +{
      +  "description": "With focus: passages to return (default 4, at most 8)",
      +  "type": "integer"
      +}
  4. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already establish safe read-only, idempotent behavior, yet the description adds substantial return semantics: cited_by source and twin-cluster summation, duplicate/stub id resolution to a survivor, embedded_citations against the reporter index, citation_warnings, and focus_miss behavior. The citability block (depublished/review_granted/transferred, old_rule, status_warning) discloses consequences an agent could not infer from structured fields.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

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

Front-loaded correctly with the core fetch statement, but the body is a dense, unstructured run-on that mixes citation counting, citability law, focus mechanics, and quotation policy with no segmentation. Most sentences carry information, yet the sprawl makes it harder to scan than it needs to be.

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?

For a 12-parameter tool with no output schema, the description covers the return shape thoroughly: cited_by and its source, embedded_citations, citation_warnings, focus_passages, quotable_passages, and the citability object. An agent has enough to call it correctly and interpret results without an output schema.

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%, so the schema carries the baseline; the description still adds meaning beyond it, notably the pin+focus interaction (first passage becomes the pinned page's window), focus_n bounds, and how forum_state alters cite output. These enrich parameters rather than merely restate them.

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?

Opens with a specific verb+resource: "Fetch one case: metadata, parallel citations, treatment flag, and full opinion text." It enumerates what comes back and names originating siblings (cluster_id from search_cases), so an agent can tell it apart from find_case or get_citing_cases without opening either schema.

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 concrete routing guidance: pass include_text=false to skip paging, run verify_quote for quotes typed from memory, run check_brief on the finished draft, use focus instead of reading from the opening. It does not crisply state when to choose get_case over find_case/get_citing_cases, so it stops short of a full when/when-not/alternatives statement.

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