Skip to main content
Glama

Find one case by citation or caption

find_case
Read-onlyIdempotent

Fast direct lookup: give a citation or a case caption and get THE case (or 'not decisive' with up to 5 candidates) without a full-text search. Use search_cases for topics and words. A citation ("384 U.S. 436", "Miranda v. Arizona, 384 U.S. 436, 444 (1966)", "449 F. App'x 901", "2019-Ohio-10") resolves through the reporter index; when a case name is given (in the query or as expected_case_name) and the case at that citation carries a different name, the answer is NOT decisive (problem name_mismatch) and names the case that is really there. A caption ("Miranda v. Arizona", or one distinctive name such as "Celotex") is decisive when the top match is at least twice as strong as the runner-up, or when the case name IS the caption word for word (punctuation, company suffixes and abbreviations read) for one decision in the corpus (several filings of one decision count once: the answer is the Published, reported record, the others listed in also_filed_as) -- an exact caption outranks any opinion-text match; common captions ("Smith v. Jones", "State v. Johnson") are not decisive by design. A docket number ("2D09-5223", "No. 1:15-cv-00001" with court, "17-1618") resolves through the docket index: decisive when one case carries it, otherwise problem ambiguous_docket with the candidates (a Supreme Court number also matches its cert-stage entries). The answer carries case (bluebook, url, link_md, treatment_flag), kind (citation|caption|docket), decisive, candidates, and a note when not decisive. A red, yellow or procedural case also carries treatment_flag_reason and treatment_flag_basis. A Westlaw / Lexis number whose sources disagree about the case carries database_caution. For a caption that is not decisive, the candidates whose caption carries both parties (abbreviations and acronyms read) are listed first, marked matched_by caption, with caption_matches = how many decisions carry it. A misspelt or partial caption that nothing matches ("Palsgraph v. Long Island R.R.", "City of Keller") gets suggestions appended to candidates, marked matched_by caption_fuzzy (a close spelling of the party names, or a caption that begins with the one party given), with did_you_mean; they never make the answer decisive. A caption that is word for word ONE decision's is decisive even when other decisions share a party name. case carries disposition (disposition_source headnote) when a synthetic headnote exists. 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. Short forms (MCP101): "[Name, ]303 U.S. at 288" is read through the page run of the case that holds the page; for id., ibid. or supra pass sentence (the draft sentence containing it) and quotation: id. binds to the citation before it in that sentence, never to a case named earlier in the conversation. year and quotation break a tie among caption candidates. "Miranda, 384 U.S. 436" (one name before the cite) is read as that cite with the name checked.

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": {
      "query": "<query>"
    },
    "name": "find_case"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearNoOptional: the decision year as written. Breaks a tie between candidate cases; never overrides a cite that resolves
courtNoOptional court id filter for a caption (same syntax as search_cases court); takes precedence over state
queryYesA citation, a case caption or a docket number, e.g. "410 U.S. 113", "Roe v. Wade, 410 U.S. 113 (1973)", "Roe v. Wade", "Celotex", "2D09-5223"
stateNoOptional two-letter state code (or name) narrowing a caption to that state's own courts
sentenceNoOptional: the sentence of the draft that contains this cite, as written (for id., ibid. or supra include the sentence before it). Binds id., ibid., supra and short forms ("Jones, 590 F.2d at 174") to the citation before them in it, and reads the case name written right before a bare short form
quotationNoOptional: the words quoted with this cite. Breaks a tie between candidate cases: the one whose opinion holds the words
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.
expected_case_nameNoThe case name the citation is supposed to be; the answer is not decisive when the case at the citation carries a different name

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. Changed3 schema fields changed
    • addedInput schema / properties / quotation
      Added value: +{
      +  "description": "Optional: the words quoted with this cite. Breaks a tie between candidate cases: the one whose opinion holds the words",
      +  "type": "string"
      +}
    • addedInput schema / properties / sentence
      Added value: +{
      +  "description": "Optional: the sentence of the draft that contains this cite, as written (for id., ibid. or supra include the sentence before it). Binds id., ibid., supra and short forms (\"Jones, 590 F.2d at 174\") to the citation before them in it, and reads the case name written right before a bare short form",
      +  "type": "string"
      +}
    • addedInput schema / properties / year
      Added value: +{
      +  "description": "Optional: the decision year as written. Breaks a tie between candidate cases; never overrides a cite that resolves",
      +  "type": "integer"
      +}
  3. Changed1 schema field changed
    • changedInput schema / properties / query / description
      Previous value: -"A citation or a case caption, e.g. \"410 U.S. 113\", \"Roe v. Wade, 410 U.S. 113 (1973)\", \"Roe v. Wade\", \"Celotex\""New value: +"A citation, a case caption or a docket number, e.g. \"410 U.S. 113\", \"Roe v. Wade, 410 U.S. 113 (1973)\", \"Roe v. Wade\", \"Celotex\", \"2D09-5223\""
  4. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already mark this as read-only, idempotent, non-destructive, and closed-world, but the description adds substantial behavioral detail: decisiveness thresholds, candidate ordering, treatment flags, database_caution, citability warnings, and short-form binding. It does not contradict any annotation.

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

Conciseness2/5

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

The opening is well front-loaded, but the rest is a single enormous paragraph with dense parenthetical clauses and niche edge cases such as California depublication rules, old_rule, and MCP101 short forms. It is information-rich but not concise or easy to scan, and it would benefit from structure or trimming.

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?

There is no output schema, so the description carries the burden of explaining returns, and it does so thoroughly: case fields, kind, decisive, candidates, note, treatment indicators, citability, database_caution, and fuzzy suggestions. For a complex legal lookup tool, the definition covers the important edge cases.

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%, and the schema already explains year, court, state, sentence, quotation, forum_state, and expected_case_name in detail. The description reinforces those meanings and adds some integrated behavior, but most parameter semantics are already supplied by the schema rather than added here.

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: 'Fast direct lookup: give a citation or a case caption and get THE case'. It explicitly distinguishes this from search_cases, so an agent can tell when this tool is the right choice without 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 Guidelines5/5

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

It names the alternative directly: 'Use search_cases for topics and words', and it explains which inputs (citation, caption, docket number, short forms) this tool handles. The guidance is explicit enough to route an agent between direct lookup and full-text search.

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