Skip to main content
Glama

Find a court id

find_court
Read-onlyIdempotent

Resolve a court name to court_id values usable in the search_cases court filter. Also resolves whole GROUPS of courts (tribal courts, veterans, bankruptcy, all U.S. district courts) to the single aggregate token that filters on all of them: see court_groups in the result. Each court row carries bluebook, the Bluebook court abbreviation for a citation parenthetical (e.g. "Fla. 1st DCA"; "U.S." for the U.S. Supreme Court, whose case citations to U.S. / S. Ct. carry no court in the parenthetical; absent for courts with none on file); citation_string is the stored CourtListener string.

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

Input Schema

NameRequiredDescriptionDefault
nameYesCourt name or group, e.g. "Florida", "Eleventh Circuit", "Texas Supreme", "Navajo Nation", "tribal courts", "veterans", "bankruptcy"

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/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 the safety profile is covered. The description adds value beyond that by disclosing the shape of the response — court_groups aggregate tokens, per-row bluebook abbreviations, and citation_string — which matters because there is no output schema. It stops short of describing no-match behavior or whether results are a list.

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?

Front-loaded with the core resolve-to-id purpose, then the group behavior, then per-row field meanings. The long Bluebook parenthetical is informative but slightly over-extended for a single field.

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 one-parameter read-only lookup with no output schema, the description covers purpose, call-site routing, group semantics, and the meaning of every returned field. An agent has enough to call it correctly and to interpret the result without further docs.

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 name parameter's examples (Florida, Eleventh Circuit, Navajo Nation, tribal courts, veterans, bankruptcy) already appear in the schema. The description adds the semantic consequence — that group names collapse to a single aggregate token in court_groups — but no syntax or matching-rule details (fuzzy vs exact, partial names).

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?

States a specific verb (resolve) and resource (court name → court_id), and explicitly ties the output to the search_cases court filter, which separates it from siblings like find_case or search_cases. It also pre-empts a likely misconception by covering whole-group resolution in the same sentence.

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?

The opening sentence gives clear context for when to reach for it: before filtering cases by court, resolve the name first. It names the downstream consumer (search_cases court filter) but offers no explicit exclusion or 'use X instead when…' guidance versus the other find_* 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