F
licenseNot graded
qualityB
maintenanceEnables LLM-friendly access to the CourtListener legal database and eCFR for searching legal opinions, court cases, judges, documents, and federal regulations.
13
-
courtlistener-mcp-server
Server Details
Search US court opinions, federal dockets, judges, citations, and oral arguments via CourtListener.
If you are the author of this connector, you can claim ownership by verifying the domain or GitHub account it belongs to. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
- Status
- Healthy
- Uptime
- 99.9% over 69 days
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-11-25
- URL
- Repository
- cyanheads/courtlistener-mcp-server
- GitHub Stars
- 4
- Server Listing
- @cyanheads/courtlistener-mcp-server
TDQS
A4.2/5.0
Scored across 14 tools
Disambiguation4/5
Each entity has a clear search/get pairing (dockets, judges, opinions, oral arguments, financial disclosures), so boundaries are mostly distinct. The only real friction is courtlistener_get_citations vs courtlistener_lookup_citation, which sound similar but serve different purposes (precedent network traversal vs. citation resolution); descriptions clarify this, though the names alone could mislead.
Naming Consistency5/5
All 14 tools follow a strict courtlistener_<verb>_<noun> pattern using get_, search_, and lookup_ prefixes consistently. The convention is predictable and immediately readable, with no mixing of styles or casing.
Tool Count5/5
14 tools is well within the ideal 3-15 range and each maps to a distinct resource or operation. No tool feels redundant or bolted on; the count matches the breadth of the legal research domain cleanly.
Completeness4/5
Coverage is strong: search and fetch pairs for judges, dockets, parties, opinions, oral arguments, financial disclosures, plus court discovery and citation resolution. The notable gap is retrieving the actual RECAP document text — the docket tool reports is_available copies but no tool fetches them, forcing a dead end for full-text documents.
Available Tools
14 toolscourtlistener_get_citationsGet Citation NetworkARead-onlyInspect
Retrieve the citation network for an opinion cluster. Supports two directions: "cited_by" (opinions that cite this one — measures precedential influence) and "citing" (opinions this one cites — reveals the authority chain relied on). This is the primary tool for tracing legal precedent chains. Note: the free tier supports shallow traversal — following 1–2 hops of a single case is practical; deep multi-hop analysis burns through the daily budget quickly.
| Name | Required | Description | Default |
|---|---|---|---|
| court | No | Filter results to a specific court (e.g., "scotus", "ca9"). Applies to both directions. | |
| cursor | No | Pagination cursor from next_cursor. For citing, a nonnegative safe decimal integer offset; for cited_by, an opaque upstream token. | |
| direction | No | "cited_by" (default): opinions that cite this one — measures precedential influence and downstream adoption. "citing": opinions this one cites — reveals the authority chain the court relied on. | cited_by |
| page_size | No | Positive requested size (default 20), bounded to 20. cited_by has an upstream minimum of 20; citing slices at most 20 cited IDs by the bounded size before filtering. Full upstream pages are preserved. Final or filtered pages can be smaller or empty; retain next_cursor to continue. page_sizing distinguishes requested, bounded and actual sizes. A normal call costs three requests plus extra variant pages. | |
| cluster_id | Yes | Opinion cluster ID to retrieve citations for. Obtain from courtlistener_search_opinions or courtlistener_lookup_citation. | |
| filed_after | No | Limit to citations filed after this date (ISO 8601). For "cited_by", useful for "how has this precedent been applied recently?" |
Output Schema
| Name | Required | Description |
|---|---|---|
| error | No | Present when the call failed. Absent on success. |
| notice | No | Context when no citations are returned — either that this page had no match under the filters and more pages remain, or a recovery hint echoing direction and filters. |
| results | No | Related opinions in the citation network. |
| direction | No | Direction of the citation relationship returned. |
| totalCount | No | Exact total for the fetched direction when source variants are complete; absent when total_is_partial is true. For cited_by this counts matching clusters after filters; for citing it counts distinct cited opinions before any filter, which can exceed the cluster rows. |
| next_cursor | No | Pagination cursor for the next page; null when no more results. |
| page_sizing | No | Requested, bounded, and actual page sizes. |
| observed_total | No | Citation total observed from the fetched source variants; a lower bound when total_is_partial is true. |
| source_case_name | No | Case name for the source cluster. |
| total_is_partial | No | True when citation results and totals are based on an incomplete source-variant set. |
| source_cluster_id | No | The cluster ID this citation network is for. |
| source_variants_completion | No | Completion of the source opinion-variant walk. |
TDQS
A4.1/5.0
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already cover the safety profile (readOnlyHint=true, openWorldHint=true, idempotentHint=false). The description adds real behavioral context the annotations don't: the free-tier budget constraint and the practical limit of 1-2 hops before cost escalates.
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 sentences, front-loaded with purpose and direction semantics, with the budget caveat placed last where it belongs. Slightly verbose in re-explaining the same two directions the schema already documents, which costs a point.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness4/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
An output schema exists, so return values need no explanation, and the free-tier constraint is a genuinely useful addition. It stops short of 5 mainly because pagination and the multi-request cost model are left entirely to the schema rather than being reinforced at the description level.
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 the baseline is 3. The description restates the semantic intent of the 'direction' enum (influence vs authority chain) but adds little beyond what the schema's own enum description already says, and says nothing extra about court, cursor, or page_size.
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 and resource ('Retrieve the citation network for an opinion cluster') and immediately disambiguates the two traversal directions, so an agent can distinguish it from siblings like courtlistener_lookup_citation without opening a 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?
Declares itself 'the primary tool for tracing legal precedent chains' and gives a use case per direction (recent application via filed_after, authority chain via citing). It never explicitly names an alternative tool or a when-not-to-use condition, so it stops short of full routing guidance.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
courtlistener_get_docketGet DocketARead-onlyIdempotentInspect
Fetch full docket metadata and entry list for a single federal case by docket ID. Returns all available docket entries with document availability status. Documents with is_available=true have a RECAP-stored copy; others require a PACER account. Obtain docket IDs from courtlistener_search_dockets or from opinion results.
| Name | Required | Description | Default |
|---|---|---|---|
| docket_id | Yes | Docket ID from a search result's docket_id field or from an opinion cluster result. | |
| entries_page | No | Page of docket entries to fetch (1-indexed). Docket entries are page-paginated at 20 per page; pass the next_cursor from a previous response here to page through large cases. | |
| entries_page_size | No | Requested docket entries per page. NOTE: CourtListener ignores this value — /docket-entries/ always returns a fixed 20-entry page regardless of what is passed. Use entries_page to reach entries beyond the first 20 (large cases can have hundreds). |
Output Schema
| Name | Required | Description |
|---|---|---|
| cause | No | Legal cause of action. |
| court | No | Court display name for major federal courts; the court identifier otherwise. |
| error | No | Present when the call failed. Absent on success. |
| entries | No | Docket entries for this page (fixed at 20 per page; entries_page_size is not honored by upstream). |
| court_id | No | Court identifier — the stable value for filtering. |
| case_name | No | Short case name. |
| docket_id | No | Docket ID. |
| date_filed | No | Date the case was filed. |
| assigned_to | No | Assigned judge name; null if not recorded. |
| jury_demand | No | Jury demand status. |
| next_cursor | No | Next page number to pass as the `entries_page` argument (docket entries are page-paginated); null when this is the last page. |
| page_sizing | No | Requested, bounded, and actual page sizes. |
| referred_to | No | Referred judge name; null if not recorded. |
| entries_page | No | Current entries page number (1-indexed). |
| docket_number | No | Docket number. |
| pacer_case_id | No | PACER case ID; null if not in RECAP. |
| total_entries | No | Total number of docket entries available; null when upstream supplies no numeric total. May exceed the returned entries list. |
| case_name_full | No | Full case name. |
| date_terminated | No | Date the case was terminated; null if active. |
| jurisdiction_type | No | Jurisdiction type. |
TDQS
A4.3/5.0
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Beyond the readOnlyHint/idempotentHint annotations, it discloses meaningful behavior: entries come with document availability status, is_available=true means a RECAP-stored copy exists, and others require a PACER account. This PACER/RECAP distinction is exactly the kind of context annotations cannot carry.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
Four tightly packed sentences, front-loaded with the purpose, then availability semantics, then input sourcing. Every sentence carries distinct information with no redundancy.
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 an output schema present, return values need no prose explanation; the description covers purpose, the RECAP/PACER availability caveat, and how to obtain the ID. Nothing an agent needs to call it correctly is missing.
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 itself is unusually thorough (including the note that entries_page_size is ignored and entries_page drives pagination). The description adds nothing parameter-specific beyond reiterating docket ID sourcing, so the 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?
States a specific verb (Fetch) and resource (full docket metadata and entry list) with clear scope (a single federal case by docket ID). This clearly distinguishes it from the sibling courtlistener_search_dockets, which finds cases rather than returning one case's contents.
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?
Explicitly tells the agent where to get the required input: 'Obtain docket IDs from courtlistener_search_dockets or from opinion results,' which establishes the search-then-fetch workflow. It does not name a when-not or a conflicting alternative, so it stops short of the top tier.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
courtlistener_get_financial_disclosureGet Financial DisclosureARead-onlyIdempotentInspect
Fetch a judicial financial disclosure by disclosure_id from courtlistener_search_financial_disclosures. Returns metadata, counts and typed line items with coded values decoded to dollar ranges. Select categories or omit for all. Oversized selections return outline then page responses; continue retrieval.next_cursor as cursor with the unchanged ID/categories selection until null. Large individual row fields remain recoverable through text_chunks.
| Name | Required | Description | Default |
|---|---|---|---|
| cursor | No | Retrieval next_cursor from the previous response. Repeat the original ID and sections/categories selection unchanged; omit to start. | |
| categories | No | Line-item categories to select. Omit for all. Oversized selections page; keep this selection unchanged while following cursor. | |
| disclosure_id | Yes | Financial disclosure ID — the disclosure_id field from a courtlistener_search_financial_disclosures result. |
Output Schema
| Name | Required | Description |
|---|---|---|
| kind | No | 'full' carries a small selected record; 'outline' pages the section catalog; 'page' carries typed rows and field-path text chunks. Filing identity and counts remain present. |
| year | No | Filing year. |
| debts | No | Debts and liabilities. |
| error | No | Present when the call failed. Absent on success. |
| gifts | No | Reported gifts. |
| counts | No | Count of line items in each disclosure category. |
| pdf_url | No | URL to the source disclosure PDF; null if unavailable. |
| sections | No | Category catalog in declared order, with paged metadata fields. Follow retrieval.next_cursor to finish the catalog and retrieve data. |
| person_id | No | Person ID of the filer — pass to courtlistener_get_judge; null if absent. |
| positions | No | Outside positions. |
| retrieval | No | Caller retrieval completion, separate from upstream source completion. |
| agreements | No | Continuing agreements. |
| is_amended | No | True if this filing is an amendment. |
| page_count | No | Page count of the source filing; null if not recorded. |
| investments | No | Investment holdings. |
| report_type | No | Report type (Nomination, Initial, Annual, Final, or Unknown). |
| disclosure_id | No | Financial disclosure ID. |
| reimbursements | No | Reimbursements. |
| spouse_incomes | No | Spouse income sources. |
| retrieval_notice | No | How to continue bounded retrieval using the unchanged ID and selection. |
| has_been_extracted | No | True if line items were parsed from the PDF; category arrays are empty when false. |
| non_investment_incomes | No | Non-investment income sources. |
TDQS
A4.6/5.0
Behavior5/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint and idempotentHint, yet the description adds substantial behavior: oversized selections return an outline then page responses, next_cursor must be followed with the unchanged ID/categories selection until null, and large row fields are recoverable via text_chunks. This is genuine operational context beyond the 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.
Conciseness4/5
Is the description appropriately sized, front-loaded, and free of redundancy?
Front-loads the core purpose and then packs pagination, decoding, and recovery details into dense but relevant sentences. Every sentence earns its place, though the middle section is somewhat compressed and technical.
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?
An output schema exists, so return values need not be re-explained, and the description still covers decoding of coded values, the paging protocol, cursor continuation, and large-field recovery. Nothing essential for correct invocation is missing.
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 baseline is 3, but the description adds real meaning: categories can be selected or omitted for all, and cursor must be continued with the unchanged selection. That constraint on cursor usage is not derivable from the schema alone, pushing it above baseline.
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 (Fetch) plus resource (judicial financial disclosure) and pins the identifier source (disclosure_id from courtlistener_search_financial_disclosures). This clearly distinguishes it from the sibling search tool and the other get_* tools that operate on different resources.
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?
It names the sibling search_financial_disclosures as the origin of the ID, implying the fetch-after-search workflow, and describes the pagination follow-up path. It does not explicitly state when not to use it, 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.
courtlistener_get_judgeGet Judge ProfileARead-onlyIdempotentInspect
Fetch full biographical profile for a single judge: positions on record — judicial appointments across all courts plus non-judicial roles — education, political affiliations, and ABA ratings. The position list is paginated upstream and walked under a page bound; the response reports whether it was truncated. Obtain person IDs from courtlistener_search_judges results.
| Name | Required | Description | Default |
|---|---|---|---|
| person_id | Yes | Judge person ID from a search result's person_id field. Identifies a specific judge across all courts they have served on. |
Output Schema
| Name | Required | Description |
|---|---|---|
| dob | No | Date of birth as CourtListener stores it, always full ISO 8601 — but the month and day are placeholders unless dob_granularity is "day". Read dob_granularity before presenting this as an exact date. Null if not recorded. |
| dod | No | Date of death as CourtListener stores it, always full ISO 8601 — precision qualified by dod_granularity, as with dob. Null if living or not recorded. |
| name | No | Full name. |
| error | No | Present when the call failed. Absent on success. |
| fjc_id | No | Federal Judicial Center ID for cross-referencing with FJC data; null if not available. |
| gender | No | Gender. |
| notice | No | Present only when positions[] was truncated: what was withheld. |
| dob_city | No | City of birth; null if not recorded. |
| dob_state | No | State of birth; null if not recorded. |
| education | No | Educational history. |
| person_id | No | Person ID. |
| positions | No | Positions on record, across all courts — judicial appointments plus non-judicial roles (private practice, prosecutor, professor), which carry no court and describe themselves in job_title. CourtListener paginates this list and the walk is bounded, so read the truncated flag before treating it as a complete career. |
| truncated | No | True when the bounded /positions/ page walk stopped with pages outstanding — positions[] is then a prefix of the person's record, not the whole of it. False when the walk reached the end. |
| aba_ratings | No | ABA qualification ratings, expanded to readable labels (e.g., "Well Qualified"). |
| positionsShown | No | Number of position records returned. |
| dob_granularity | No | Precision actually recorded for dob: "year", "month", or "day". Null when CourtListener recorded no precision. An unrecognized upstream value passes through unchanged. |
| dod_granularity | No | Precision actually recorded for dod: "year", "month", or "day". Null when CourtListener recorded no precision. |
| political_affiliations | No | Political affiliation history. |
TDQS
A4.3/5.0
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnly and idempotent. The description adds genuinely useful behavior: the position list is paginated upstream, walked under a page bound, and the response reports whether it was truncated. That is real context beyond the annotations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
Three sentences, front-loaded with the content listing, followed by the pagination caveat and the ID provenance. No filler.
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 an output schema present, return values need no explanation; the description still flags truncation reporting, which is the one behavioral nuance an agent needs. Nothing material is missing for a single-parameter read 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 coverage is 100% and the single person_id is fully documented in the schema, including its provenance. The description's pointer to search results mostly repeats the schema, so baseline 3 is correct.
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 (Fetch) and resource (full biographical profile for a single judge), then enumerates the contents: positions, education, political affiliations, ABA ratings. An agent can distinguish this from courtlistener_search_judges immediately.
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?
Explicitly routes the agent to courtlistener_search_judges as the source of person IDs, which is the key prerequisite. It does not state any when-not condition or alternative retrieval paths, so it falls short of a 5.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
courtlistener_get_opinionGet Court OpinionARead-onlyIdempotentInspect
Fetch text and metadata for an opinion cluster by cluster ID. Returns majority, concurrence and dissent variants with raw HTML and readable plain text, variants_completion for source coverage, and docket_enrichment. Oversized selections return outline then page responses; continue retrieval.next_cursor as cursor with the unchanged ID/sections selection until null. Obtain cluster IDs from courtlistener_search_opinions, courtlistener_lookup_citation, or docket results.
| Name | Required | Description | Default |
|---|---|---|---|
| cursor | No | Retrieval next_cursor from the previous response. Repeat the original ID and sections/categories selection unchanged; omit to start. | |
| sections | No | Opinion variant identifiers to select (e.g. ["opinion_12345"]). Omit for all fetched variants. Oversized selections page; keep this selection unchanged while following cursor. | |
| cluster_id | Yes | Opinion cluster ID — identifies a case decision and groups all opinion variants (majority, concurrence, dissent). Obtain from courtlistener_search_opinions, courtlistener_lookup_citation, or from docket results that link to opinions. |
Output Schema
| Name | Required | Description |
|---|---|---|
| kind | No | 'full' carries a small selected record; 'outline' pages the section catalog; 'page' carries typed rows and field-path text chunks. Bounded identity remains present throughout retrieval. |
| court | No | Court display name. |
| error | No | Present when the call failed. Absent on success. |
| judges | No | Judge names. |
| posture | No | Procedural posture (may be empty). |
| court_id | No | Court identifier. |
| opinions | No | Fetched variants; variants_completion describes source coverage. Pages can contain partial typed variants; omitted text is recoverable through retrieval.text_chunks at original field paths. |
| sections | No | Section catalog in source order, including paged metadata. Only opinion_<id> names select variants; follow retrieval.next_cursor to finish the catalog and retrieve data. |
| syllabus | No | Syllabus text (may be empty). |
| case_name | No | Short case name. |
| citations | No | All known citation strings for this case. |
| docket_id | No | Associated docket ID. |
| retrieval | No | Caller retrieval completion, separate from upstream source completion. |
| cite_count | No | Total number of citations from other opinions. |
| cluster_id | No | Opinion cluster ID. |
| date_filed | No | Date the opinion was filed. |
| docket_number | No | Docket number. |
| case_name_full | No | Full case name with parties. |
| retrieval_notice | No | How to continue bounded retrieval using the unchanged ID and selection. |
| docket_enrichment | No | Linked-docket enrichment outcome, independent of opinion text availability. |
| precedential_status | No | Publication/precedential status. |
| variants_completion | No | Source-walk completion. An oversized upstream next_cursor is omitted on partial responses and recovered at /variants_completion/next_cursor through retrieval.text_chunks. |
TDQS
A4.6/5.0
Behavior5/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already cover readOnlyHint and idempotentHint, but the description adds substantial behavioral context: the variant structure, raw HTML plus plain text, variants_completion source coverage, docket_enrichment, and the oversized-selection pagination protocol (outline then pages, repeat unchanged selection until cursor is null). This is exactly the extra depth the annotations do not provide.
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 sentences, front-loaded with the core action, then returns, then pagination, then ID sourcing. Dense but each sentence carries distinct information; minor overlap between the description and schema text on cursor/sections keeps it from a 5.
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 an output schema present, return values need not be explained, yet the description still sketches them, and it fully covers the pagination continuation behavior and ID provenance. Nothing an agent needs to invoke this correctly is missing.
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 baseline is 3, but the description adds real meaning beyond the schema: it maps retrieval.next_cursor to the cursor param and stresses the invariant that ID/sections must stay unchanged while following the cursor. That pagination contract is not obvious from the schema alone.
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 (fetch) and resource (text and metadata for an opinion cluster) keyed by cluster ID, and specifies the returned variant types (majority, concurrence, dissent). An agent can distinguish this read of a single opinion cluster from search or lookup siblings 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 Guidelines4/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
Explicitly routes the agent to courtlistener_search_opinions, courtlistener_lookup_citation, or docket results for obtaining cluster IDs, and explains the cursor-continuation workflow. It stops short of naming a when-not-to-use alternative among the get_* siblings, so it is clear context rather than full exclusion guidance.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
courtlistener_get_oral_argumentGet Oral ArgumentARead-onlyIdempotentInspect
Fetch an oral argument recording by audio_id from courtlistener_search_oral_arguments. Returns case metadata, panel IDs, duration, MP3 URL, docket and available transcript. Oversized text or metadata returns outline then page responses; continue retrieval.next_cursor as cursor with the unchanged ID/sections selection until null. The argument date comes from search or the linked docket.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | Audio recording ID — the audio_id field from a courtlistener_search_oral_arguments result. | |
| cursor | No | Retrieval next_cursor from the previous response. Repeat the original ID and sections/categories selection unchanged; omit to start. | |
| sections | No | Selected record fields. Metadata is always selected; a nonempty selection omitting transcript excludes it. Omit for the whole record. Oversized selections page; keep this selection unchanged while following cursor. |
Output Schema
| Name | Required | Description |
|---|---|---|
| kind | No | 'full' carries a small selected record; 'outline' pages the section catalog; 'page' carries fields and text chunks. Bounded identity remains present throughout retrieval. |
| error | No | Present when the call failed. Absent on success. |
| judges | No | Free-text judge names; often empty on this endpoint. |
| sections | No | Section catalog: transcript and paged metadata fields. Follow retrieval.next_cursor to finish the catalog and retrieve data. |
| case_name | No | Case name. |
| docket_id | No | Associated docket ID; 0 if not linked. |
| panel_ids | No | Person IDs of panel judges — pass to courtlistener_get_judge. |
| retrieval | No | Caller retrieval completion, separate from upstream source completion. |
| transcript | No | Speech-to-text transcript; empty if transcription has not completed. Oversized text is recovered through retrieval.text_chunks at /transcript. |
| download_url | No | Direct MP3 download URL; null if not available. |
| case_name_full | No | Full case name with parties. |
| has_transcript | No | True if a speech-to-text transcript is available. |
| duration_seconds | No | Recording duration in seconds. |
| oral_argument_id | No | Audio recording ID. |
| retrieval_notice | No | How to continue bounded retrieval using the unchanged ID and selection. |
TDQS
A4.1/5.0
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations only declare readOnlyHint and idempotentHint, so the description's disclosure that oversized text/metadata responses are split into outline-then-page results, that paging continues until next_cursor is null, and that the argument date must come from search or the linked docket is genuinely additive. It does not cover auth or rate-limit behavior, which keeps it below 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?
Front-loaded with the purpose and the ID source, then the return contents, then the paging mechanics in a compact four sentences. The paging sentence is dense and slightly hard to parse on first read, but nothing is wasted or redundant.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness4/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With an output schema present the description need not enumerate return values, yet the outlined list (metadata, panel IDs, duration, MP3 URL, docket, transcript) plus the cursor-continuation rule gives an agent everything needed to call and resume correctly. Only permissions/error behavior is unaddressed, which is low-stakes for an annotated read-only 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 the baseline is 3; the schema already documents id, cursor, and sections thoroughly, including the rule that metadata is always selected. The description largely restates the cursor/sections paging contract the schema already carries, adding little parameter-level meaning beyond it.
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 and resource ("Fetch an oral argument recording") and names the exact source of the identifier, tying it to courtlistener_search_oral_arguments rather than any sibling like get_docket or get_opinion. An agent can immediately tell this is the retrieve-one-by-ID counterpart to the oral-argument search tool. The only nit is that the description calls the key "audio_id" while the schema parameter is "id", but the schema's own description reconciles this.
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?
It gives a clear entry condition — you call this after a search_oral_arguments result supplies the ID — and explains the pagination follow-up (repeat next_cursor with the unchanged ID/sections until null). There is no explicit when-not or alternative-selection statement, so it stops short of full routing guidance.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
courtlistener_get_partiesGet PartiesARead-onlyIdempotentInspect
Fetch a page of parties and their attorneys of record for a RECAP federal docket by docket ID. Returns each party's name, role (Plaintiff, Defendant, Petitioner, Respondent, etc.), and their attorneys with contact information, scoped to this docket. Costs one party request plus up to five attorney roster requests. A later roster page blocked by the local request budget returns fetched detail with capped resolution, unresolved IDs, and the remaining roster cursor. Obtain docket IDs from courtlistener_search_dockets or courtlistener_get_docket.
| Name | Required | Description | Default |
|---|---|---|---|
| cursor | No | Pagination cursor from a previous response's next_cursor field. Omit for the first page. This is an opaque token, not a page number — CourtListener cursor-paginates this endpoint, so a numeric value selects nothing and re-serves the first page. | |
| docket_id | Yes | Docket ID from a courtlistener_search_dockets or courtlistener_get_docket result's docket_id field. | |
| page_size | No | Positive requested party page size (default 10), bounded to 10 before retrieval. CourtListener uses fixed 20-row pages and ignores this request; final pages can be smaller. page_sizing reports requested, bounded and actual sizes. |
Output Schema
| Name | Required | Description |
|---|---|---|
| error | No | Present when the call failed. Absent on success. |
| parties | No | Parties on this page. |
| docket_id | No | Docket ID these parties belong to. |
| totalCount | No | Total parties on this docket across all pages — this endpoint reports its count as a URL rather than a number, so the total is only derivable when the first page is also the last, and is absent for any list spanning more than one page. |
| next_cursor | No | Opaque pagination cursor for the next page — pass it back as the `cursor` argument; null when this is the last page. |
| page_sizing | No | Requested, bounded, and actual page sizes. |
| total_parties | No | Total parties on this docket across all pages; null when no total is derivable — CourtListener serves the count as a URL rather than a number here, so it is only known when the first page is also the last. |
| attorney_resolution | No | Attorney lookup completeness; no additional automatic requests are made. |
TDQS
A4.4/5.0
Behavior5/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Goes well beyond the readOnlyHint/idempotentHint annotations by disclosing the cost model (one party request plus up to five attorney roster requests), the local request-budget blocking behavior, and the degraded response shape (capped resolution, unresolved IDs, remaining roster cursor). This is exactly the operational context an agent needs before calling.
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 purpose, then returns, cost, edge case, and prerequisite in a logical order. Every sentence carries information, though the description is somewhat dense and the return-value sentence overlaps with the available output schema.
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?
Given an output schema and safety annotations already exist, the description still supplies the cost/budget caveats and the ID-sourcing prerequisite, leaving nothing an agent needs to invoke it correctly. The request-budget degradation behavior is particularly valuable and not recoverable from structured fields.
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 the schema already documents docket_id, cursor, and page_size thoroughly. The description's mention of a 'roster cursor' adds a little relational context, but it does not clarify parameter behavior beyond what the schema provides, so 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?
States a specific verb and resource ('Fetch a page of parties and their attorneys of record'), names the scope ('for a RECAP federal docket by docket ID'), and enumerates the returned fields. No sibling tool fetches parties, so it is trivially distinguishable from the rest of the family.
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?
Explicitly routes the agent to obtain the required docket_id from courtlistener_search_dockets or courtlistener_get_docket, which is the key prerequisite. It lacks an explicit when-not or alternative-selection clause, but no sibling performs this function, so the omission is minor.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
courtlistener_lookup_citationLookup Legal CitationARead-onlyIdempotentInspect
Resolve legal citations (e.g., "410 U.S. 113", "93 S. Ct. 705") to opinion cluster IDs and case metadata. Enables workflows that start from a known citation rather than a search query. CourtListener extracts every citation it finds in the submitted text, so passing a passage returns one entry per citation, each with its own resolution status — an unresolved or ambiguous citation is reported in the results, not raised as an error. Supports standard US reporter formats. Costs one request against CourtListener's per-citation quota, plus one ordinary request per distinct docket whose court is resolved — max_court_lookups bounds that second half (default 4, set 0 to skip court resolution entirely). CourtListener meters this endpoint by citations submitted rather than by call, so a long passage spends proportionally more of that quota. Requires authentication — uses the CourtListener /citation-lookup/ endpoint.
| Name | Required | Description | Default |
|---|---|---|---|
| citation | Yes | Text to extract citations from — normally a single citation (e.g., "410 U.S. 113", "347 U.S. 483", "93 S. Ct. 705"), but any passage works and every citation in it is resolved. Supports standard reporter formats. Up to 64000 characters, which is CourtListener's own ceiling; a longer passage is rejected here rather than spending a request to be refused upstream. | |
| max_court_lookups | No | How many distinct dockets this call may spend a request on to resolve cluster courts. The lookup itself is metered separately by CourtListener (per citation submitted), so this budget is drawn entirely from the ordinary per-request allowance — published free tier 5/min, 50/hour, 125/day, varying by token tier. 0 skips court resolution and costs nothing beyond the lookup; 20 is the ceiling. Clusters past the budget come back with court null and court_resolution "over_budget". |
Output Schema
| Name | Required | Description |
|---|---|---|
| error | No | Present when the call failed. Absent on success. |
| notice | No | Caveats on this result: a recovery hint when no citation in the input resolved to a case, and counts of the clusters whose court went unresolved — split by whether the per-call docket budget ran out or an attempted lookup returned nothing, since only the first is worth retrying with a larger budget. Absent when none applies. |
| matches | No | One entry per citation CourtListener extracted from the input, in the order they appear. |
| queriedCitation | No | The citation string that was looked up. |
TDQS
A4.6/5.0
Behavior5/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Goes well beyond the readOnly/idempotent annotations: discloses per-citation quota metering, the additional per-docket request cost, the 64000-char ceiling, the authentication requirement, and the key behavioral trait that unresolved/ambiguous citations are returned in results rather than raised as errors.
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-loads the purpose and input examples, then layers cost/auth/limit details in a single dense block. Every sentence carries load, though the quota discussion is somewhat thick and could be tightened.
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?
An output schema exists so return-value documentation is unnecessary, and the description covers the remaining gaps an agent needs: auth, meter model, budget semantics, size limit, and partial-failure handling.
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 already 100%, so the baseline is 3, but the description adds real meaning: it clarifies that the quota is charged per citation submitted rather than per call (so a long passage costs more) and that max_court_lookups draws on the separate per-request allowance with clusters past budget returning court_resolution "over_budget".
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+resource ("Resolve legal citations ... to opinion cluster IDs and case metadata") and gives concrete input examples. It also distinguishes itself from the search siblings by naming the workflow it serves: "start from a known citation rather than a search query."
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?
Clearly frames the selection context (citation-first workflows vs. query-first search) and explains the max_court_lookups budget trade-off, including setting 0 to skip court resolution. It stops short of naming a specific sibling alternative the way the calibration's top example does.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
courtlistener_lookup_courtsLookup CourtsARead-onlyInspect
List courts with optional filtering by jurisdiction type, active/inactive status, and scraper coverage. Primarily used to discover court IDs for use in search and filter parameters across all other courtlistener tools. Defaults to the active bench — the courts CourtListener still scrapes; pass status:'inactive' for historical courts or status:'any' for every court. A bundled snapshot returns the complete list of matching court IDs without paging whenever the filtered set fits the response budget, which covers the default bench and every jurisdiction filter. Full court records — names, citation strings, scraper status — come live from CourtListener at a fixed 20 rows per page, so pull those only when a court ID alone is not enough.
| Name | Required | Description | Default |
|---|---|---|---|
| page | No | Page number (1-indexed). CourtListener serves /courts/ at a fixed 20 rows per page and ignores any requested page size, so the number of pages is the enrichment totalCount divided by 20 — there is no way to pull a larger page. Pass the next_cursor from a previous response here to walk them one call at a time. | |
| status | No | Which bench to return. 'active' (default) returns only courts CourtListener currently scrapes; 'inactive' returns only the historical and defunct courts it no longer scrapes; 'any' returns both. The two filtered sets are disjoint, so 'any' is the only value that reaches the whole list — but reaching all of it means paging, one call per 20 courts, and the inactive bench is several times larger than the active one. Prefer the narrowest value that answers the question, and narrow with jurisdiction rather than paging the full list. | active |
| jurisdiction | No | Jurisdiction type — CourtListener's own court classification, one code per court: F=Federal Appellate, FD=Federal District, FB=Federal Bankruptcy, FBP=Federal Bankruptcy Panel, FS=Federal Special, S=State Supreme, SA=State Appellate, ST=State Trial, SS=State Special, SAG=State Attorney General, TRS=Tribal Supreme, TRA=Tribal Appellate, TRT=Tribal Trial, TRX=Tribal Special, TS=Territory Supreme, TA=Territory Appellate, TT=Territory Trial, TSP=Territory Special, MA=Military Appellate, MT=Military Trial, C=Committee, I=International. Omit to list all. SCOTUS and the numbered circuits are F; USITC and FISC are FS. Upstream's Testing code is not offered here: /courts/ excludes testing courts from every response, so a filter on it can only ever return nothing. Accepted but matching no court as of the 2026-07-30 snapshot: TSP, MT. Courts whose stored jurisdiction is not one of these codes (njcirctsussex, ohctapp1) are unreachable through this filter at any value — the value they store is not one the filter accepts. Pass those ids straight to the tool that needs them, or list with no jurisdiction filter. | |
| has_opinion_scraper | No | Filter to courts with active opinion scraping. Useful when planning search queries — courts without scrapers have sparse coverage. |
Output Schema
| Name | Required | Description |
|---|---|---|
| page | No | Current page number (1-indexed). |
| error | No | Present when the call failed. Absent on success. |
| courts | No | Matching courts on this page. |
| notice | No | Recovery hint when no courts match the applied filters. |
| totalCount | No | Total courts returned. |
| next_cursor | No | Next page number to pass as the `page` argument (this list is page-paginated at a fixed 20 rows/page); null when this is the last page — a non-null value means the courts shown are a partial view of the filtered set. |
| all_matching_court_ids | No | Every court id matching the same filters, from a snapshot of /courts/ bundled with this server (taken 2026-07-30) — the complete set, not just this page, and free of any request. Paging `courts` is only needed for the fields a court id alone does not carry (full_name, citation_string, scraper flags). Empty when more than 1000 courts match, since a prefix of the set would be indistinguishable from the whole of it — check all_matching_court_ids_complete before reading emptiness as "no courts match". A court added or retired upstream since the snapshot date appears in `courts` but may be missing here. |
| all_matching_court_ids_complete | No | True when all_matching_court_ids holds every matching court id. False when more than 1000 courts match: the list is withheld whole rather than truncated, and the notice gives the count and how to narrow. |
TDQS
A4.4/5.0
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations cover the safety profile (readOnlyHint=true, openWorldHint=true), but the description adds genuinely non-obvious behavior: a bundled snapshot serves the complete matching ID list without paging when the set fits the response budget, whereas full records come live from CourtListener at a fixed 20 rows per page. That paging/response-budget distinction is not derivable from the annotations and materially affects how an agent plans calls. Minor overlap with the schema's page description 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?
Front-loaded with purpose and the ID-discovery rationale, then the status defaults, then the paging/snapshot economics — a sensible ordering with no filler sentences. It is slightly long and repeats the '20 rows per page' constraint already stated in the page parameter description, which costs it a point.
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?
An output schema exists, so return values need not be explained. The description covers the remaining complexity an agent needs: default scope, disjoint status benches, filter narrowing, and the snapshot-vs-live paging tradeoff. Nothing required to call this four-parameter, zero-required-parameter tool correctly is missing.
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 documents status semantics and the full jurisdiction code map in more detail than the description. The description largely restates the defaults ('defaults to the active bench', status:'inactive'/'any') rather than adding new parameter meaning. Baseline 3 is appropriate when the schema does the heavy lifting.
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 and resource ('List courts') and immediately scopes it with the available filters (jurisdiction, status, scraper coverage). It also explicitly positions itself against the rest of the toolset: 'Primarily used to discover court IDs for use in search and filter parameters across all other courtlistener tools.' An agent can tell this is the ID-discovery tool rather than any of the get_/search_ siblings without opening a 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?
Gives explicit when-to-use and when-not guidance: default is the active bench, pass status:'inactive' for historical courts, status:'any' for everything, and 'pull those only when a court ID alone is not enough.' It also directs the agent to prefer the narrowest filter and to narrow with jurisdiction rather than page the full list, which is a concrete routing rule.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
courtlistener_search_docketsSearch Federal Court DocketsARead-onlyInspect
Search RECAP federal court dockets. Query terms match case name, docket number, party, and attorney names; filters narrow by party name, court, and filing date. RECAP is a crowd-sourced mirror of PACER (the federal court filing system) — coverage varies by court and date. Returns docket metadata with the parties, attorneys, and firms of record, plus up to 3 sample document entries per docket. Use courtlistener_lookup_courts to find court IDs.
| Name | Required | Description | Default |
|---|---|---|---|
| q | Yes | Query terms matched against case name, docket number, party names, and attorney names. Example: "Apple Inc patent infringement". | |
| court | No | Filter to a specific federal court ID (e.g., "dnd", "cacd", "deb" for Delaware Bankruptcy). Use courtlistener_lookup_courts to find court IDs. | |
| cursor | No | Pagination cursor from a previous response's next_cursor field. | |
| page_size | No | Positive requested page size (default 20), bounded to 20. Upstream search has a 20-row minimum; empty and final pages can be smaller. Full pages and continuation are preserved; page_sizing reports actual sizes. | |
| party_name | No | Filter to dockets listing a specific party by name — applied in addition to (AND with) the q query. More precise than including party names in q when the party name is known. | |
| filed_after | No | Earliest case filing date (ISO 8601). | |
| filed_before | No | Latest case filing date (ISO 8601). |
Output Schema
| Name | Required | Description |
|---|---|---|
| error | No | Present when the call failed. Absent on success. |
| notice | No | Recovery hint when results are empty — echoes filters and suggests how to broaden. |
| results | No | Matching docket records. |
| totalCount | No | Total matching dockets. |
| next_cursor | No | Pagination cursor for the next page; null when no more results. |
| page_sizing | No | Requested, bounded, and actual page sizes. |
| coverage_note | No | Note about RECAP coverage limitations. |
TDQS
A3.9/5.0
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, openWorldHint=true, and idempotentHint=false, so the safety profile is covered. The description adds genuine behavioral context beyond that: RECAP is a crowd-sourced PACER mirror whose coverage varies by court and date, which materially affects how an agent should interpret sparse results.
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?
Three sentences, front-loaded with purpose and free of filler. The closing sentence describing return contents is somewhat redundant given an output schema exists, which keeps this just short of a 5.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness4/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With an output schema present, the description needn't detail return shape, and annotations cover safety. It supplies the important coverage caveat and the court-ID cross-reference, leaving only minor gaps such as pagination guidance, which the schema already handles.
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 each parameter already carries a detailed description, including the party_name-vs-q precision note and pagination semantics. The description largely restates those fields (query matching surface, filter dimensions) without adding syntax or format detail, so the baseline of 3 is appropriate.
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 ("Search RECAP federal court dockets") and immediately scopes what the query matches and what the filters narrow. This cleanly distinguishes it from siblings like courtlistener_search_opinions and courtlistener_search_judges.
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?
It routes the agent to courtlistener_lookup_courts for court IDs and warns that RECAP coverage varies by court and date, which is useful context. However, it never states when to use this search versus a direct fetch like courtlistener_get_docket, nor any when-not-to-use condition, so usage is only implied.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
courtlistener_search_financial_disclosuresSearch Financial DisclosuresARead-onlyInspect
Search federal judicial financial disclosure filings — the annual reports judges file on investments, gifts, debts, outside positions, and income. Filter by judge (person ID from courtlistener_search_judges) and/or filing year; the year filter is applied to the fetched page only (CourtListener has no server-side year filter), so page through with cursor to reach a judge's filings for a year that fall on later pages. Returns per-filing metadata, category counts, itemized gifts, and a link to the source PDF. Line-item investments (often hundreds per filing, with coded values) are summarized as counts; the linked PDF carries the full itemization. Use this for judicial-ethics and recusal research after identifying a judge's person ID.
| Name | Required | Description | Default |
|---|---|---|---|
| year | No | Filing year to filter by (e.g., 2022). Applied client-side to the fetched page only — CourtListener rejects a server-side year param, so filings for this year on later pages are not included. When a page has no match for the year but more pages remain, next_cursor is returned; pass it as cursor to check the next page. Omit to return all years on the page. | |
| cursor | No | Pagination cursor from a previous response's next_cursor field. | |
| judge_id | No | Person ID of the judge whose disclosures to return — obtain from courtlistener_search_judges (the person_id field). Omit to browse across all filers. | |
| page_size | No | Positive requested page size (default 20), bounded to 20. Upstream has a minimum of 20; final pages and page-local year filtering can return fewer. Full fetched pages and continuation are preserved; page_sizing reports returned sizes. |
Output Schema
| Name | Required | Description |
|---|---|---|
| error | No | Present when the call failed. Absent on success. |
| notice | No | Recovery hint when no filings are found — echoes filters and suggests next steps. |
| results | No | Matching financial disclosure filings. |
| totalCount | No | Total matching disclosure filings — present only when the API reports a numeric count (this endpoint returns it as a URL by default, so it is usually absent). |
| next_cursor | No | Pagination cursor for the next page; null when no more results. |
| page_sizing | No | Requested, bounded, and actual page sizes. |
TDQS
A4.4/5.0
Behavior5/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Goes well beyond the readOnly/openWorld/idempotent annotations by disclosing a non-obvious upstream constraint (CourtListener rejects a server-side year param, so filtering is client-side and page-local) and the required cursor paging to reach a given year. It also flags that line-item investments are summarized as counts rather than returned in full, which materially affects expectations of the result.
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-loads what the tool is and what it filters on, then layers the paging caveat and return-shape note. It is dense and somewhat long, but nearly every clause carries operational information; the final 'use this for' sentence could have been moved earlier.
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?
An output schema exists, yet the description still usefully previews return contents (per-filing metadata, category counts, itemized gifts, PDF link) and warns about summarized line items. Combined with the paging and filtering caveats, an agent has everything needed to call it correctly.
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 parameter is already documented in the schema, including the client-side year behavior and cursor semantics. The description adds only the judge_id provenance note, which the schema also states; baseline 3 applies when the schema does the heavy lifting.
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 (Search) and resource (federal judicial financial disclosure filings), then defines the resource concretely (annual reports covering investments, gifts, debts, outside positions, income). It is clearly distinguishable from the singular sibling courtlistener_get_financial_disclosure and names courtlistener_search_judges as the source for a judge's person ID.
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?
Explicitly says to use it 'for judicial-ethics and recusal research after identifying a judge's person ID,' and gives the precondition (person ID from courtlistener_search_judges). It explains the pagination workaround for the year filter, but never contrasts itself with courtlistener_get_financial_disclosure, so the alternative-selection guidance is incomplete.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
courtlistener_search_judgesSearch JudgesARead-onlyInspect
Search judge/person records by name, appointing president, court, political affiliation, or demographic. Returns biographical data, current position, and appointment summary. Use courtlistener_get_judge for full appointment history and education records.
| Name | Required | Description | Default |
|---|---|---|---|
| q | Yes | Search query — judge name, court, city, or relevant keywords. | |
| court | No | Filter to judges who have held a position at this court (e.g., "scotus", "ca9"). Use court_id strings from courtlistener_lookup_courts. | |
| cursor | No | Pagination cursor from a previous response's next_cursor field. | |
| appointer | No | Filter by appointing president's last name (e.g., "Obama", "Trump", "Biden"). Matches against the appointer field in position records. | |
| page_size | No | Positive requested page size (default 20), bounded to 20. Upstream search has a 20-row minimum; empty and final pages can be smaller. Full pages and continuation are preserved; page_sizing reports actual sizes. | |
| political_affiliation | No | Filter by political affiliation: d=Democrat, r=Republican, i=Independent, l=Libertarian, g=Green Party, u=Unknown/unconfirmed. Based on party of the appointing president or election affiliation. |
Output Schema
| Name | Required | Description |
|---|---|---|
| error | No | Present when the call failed. Absent on success. |
| notice | No | Recovery hint when results are empty — echoes filters and suggests how to broaden. |
| results | No | Matching judge records. |
| totalCount | No | Total matching judge records. |
| next_cursor | No | Pagination cursor for the next page; null when no more results. |
| page_sizing | No | Requested, bounded, and actual page sizes. |
TDQS
A3.9/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, openWorldHint=true, and idempotentHint=false, so the safety and repeatability profile is covered. The description adds that results include biographical data, current position, and appointment summary, but says nothing about pagination behavior, throttling, or result limits beyond what the schema conveys.
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?
Three tight sentences, front-loaded with purpose and filters before the sibling pointer. The middle sentence about return contents is mildly redundant given the presence of an output schema, but it costs little.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness4/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With an output schema present, a 100% covered input schema, and annotations carrying the safety profile, the description only needs to state scope and route to the detail tool, which it does. The unexplained 'demographic' filter is the one loose end.
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 each parameter is already documented in detail (including cursor, page_size, and affiliation enum). The description restates the filter set but adds no syntax or format detail, and its mention of 'demographic' has no corresponding parameter, which is a minor inaccuracy rather than added meaning.
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?
Starts with a specific verb+resource ('Search judge/person records') and enumerates the searchable filter dimensions. It also differentiates itself from the detail sibling by name, so an agent can pick it 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?
'Use courtlistener_get_judge for full appointment history and education records' gives an explicit alternative and the condition that favors it. It lacks any stated when-not-to-use for search itself, but the routing guidance is concrete.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
courtlistener_search_opinionsSearch Court OpinionsARead-onlyInspect
Full-text search across 9M+ written US court opinions with field-level filtering. Returns opinion cluster summaries with case metadata, citations, matched text snippets, and the individual opinion variants filed in each case. Supports CourtListener field syntax (caseName:"roe v wade", court_id:scotus, judge:"Alito") and boolean operators (AND, OR, NOT). Use courtlistener_lookup_courts to find court IDs. CourtListener publishes free-tier limits of 5 req/min, 50/hr, 125/day; actual limits vary by token tier.
| Name | Required | Description | Default |
|---|---|---|---|
| q | Yes | Full-text query. Supports field syntax (caseName:"roe v wade", court_id:scotus, judge:"Alito") and boolean operators (AND, OR, NOT). Use plain English for semantic-style queries or legal citations. | |
| court | No | Filter to a specific court by court ID (e.g., "scotus", "ca9", "nyed"). Use courtlistener_lookup_courts to find court IDs. | |
| cursor | No | Pagination cursor from a previous response's next_cursor field. Omit for the first page. | |
| status | No | Opinion publication status. "Published": precedential. "Unpublished": not citable as precedent in most jurisdictions. "Errata": corrections. "Separate": separate opinion filed outside main cluster. "In-chambers": single-justice order. "Relating-to": companion or related-case order. Omit to use CourtListener’s Published default. | |
| order_by | No | Result ordering. "score desc" (default) ranks by relevance. "citeCount desc" surfaces most-cited opinions first. | score desc |
| page_size | No | Positive requested page size (default 20), bounded to 20 before retrieval. Upstream search has a 20-row minimum; empty and final pages can be smaller. Full upstream pages and continuation are preserved; page_sizing reports requested, bounded and actual sizes. | |
| filed_after | No | Earliest filing date (ISO 8601, e.g., "2020-01-01"). Narrows search to opinions filed on or after this date. | |
| filed_before | No | Latest filing date (ISO 8601). Narrows search to opinions filed before or on this date. |
Output Schema
| Name | Required | Description |
|---|---|---|
| error | No | Present when the call failed. Absent on success. |
| notice | No | Recovery hint when results are empty — echoes filters and suggests how to broaden. |
| results | No | Matching opinion cluster summaries. |
| totalCount | No | Total matching opinions in the corpus. |
| next_cursor | No | Pagination cursor for the next page; null when no more results. |
| page_sizing | No | Requested, bounded, and actual page sizes. |
| effectiveQuery | No | Query terms sent to CourtListener. |
TDQS
A4.2/5.0
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already cover the safety profile (readOnlyHint=true, openWorldHint=true, idempotentHint=false), so the bar is lower. The description still adds real behavioral context the annotations cannot carry: published free-tier rate limits (5/min, 50/hr, 125/day) that vary by token tier, plus a note that results include matched text snippets and individual opinion variants. It stops short of auth requirements or failure modes.
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?
Three front-loaded sentences: what it searches, what it returns, then syntax and limits. Dense and largely waste-free, though the field-syntax examples and court-ID pointer duplicate the schema rather than adding new information.
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 search tool with an output schema, an 8-param schema at full coverage, and annotations covering safety, the description supplies everything else an agent needs: result shape, query syntax, sibling routing for court IDs, pagination via cursor, and rate-limit constraints.
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 all eight parameters are already documented in the schema — including the same field-syntax examples and the courtlistener_lookup_courts pointer that the description repeats. The description adds essentially no parameter meaning beyond the structured fields, so the 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?
States a specific verb (full-text search), resource (9M+ written US court opinions), and scope (field-level filtering, returns cluster summaries). This is clearly distinguishable from siblings like courtlistener_get_opinion (fetch one) and courtlistener_search_dockets (docket search) 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 clear usage context: it routes the agent to courtlistener_lookup_courts for court IDs and discloses rate limits that constrain call patterns. It does not explicitly say when to prefer this over courtlistener_search_dockets or courtlistener_get_opinion, so no exclusions are stated.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
courtlistener_search_oral_argumentsSearch Oral ArgumentsARead-onlyInspect
Search appellate oral argument audio recordings — the largest public collection of oral argument audio. Returns recording metadata with two direct MP3 links per result (download_url at the originating court, local_path for CourtListener's durable copy), panel judge IDs, and transcript snippets where available. Panel judge IDs can be passed to courtlistener_get_judge for biographical context.
| Name | Required | Description | Default |
|---|---|---|---|
| q | Yes | Query terms matched against case name and transcribed argument text (where available). | |
| court | No | Filter to a specific court (e.g., "scotus", "ca9"). | |
| cursor | No | Pagination cursor from a previous response's next_cursor field. | |
| page_size | No | Positive requested page size (default 20), bounded to 20. Upstream search has a 20-row minimum; empty and final pages can be smaller. Full pages and continuation are preserved; page_sizing reports actual sizes. | |
| argued_after | No | Earliest date the case was argued (ISO 8601) — filters by argument date, not publication date. | |
| argued_before | No | Latest date the case was argued (ISO 8601). |
Output Schema
| Name | Required | Description |
|---|---|---|
| error | No | Present when the call failed. Absent on success. |
| notice | No | Recovery hint when results are empty — echoes filters and suggests how to broaden. |
| results | No | Matching oral argument recordings. |
| totalCount | No | Total matching oral argument recordings. |
| next_cursor | No | Pagination cursor for the next page; null when no more results. |
| page_sizing | No | Requested, bounded, and actual page sizes. |
TDQS
A3.7/5.0
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, openWorldHint=true, and idempotentHint=false, so the safety profile is covered. The description goes beyond them by explaining the two distinct MP3 links (download_url at the originating court vs. local_path as CourtListener's durable copy) and by flagging that transcripts are only sometimes present — non-obvious content behavior that helps an agent interpret results.
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?
Three tight sentences with the purpose front-loaded before the return-value details. The second sentence is dense but each clause carries information; no filler or restatement of the tool name.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness4/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With an output schema present, the description is not obligated to enumerate return fields, yet it usefully summarizes the shape (metadata, dual MP3 links, judge IDs, transcripts) and points to a natural next tool. An agent can invoke it correctly from description plus schema, though the lack of explicit usage/exclusion guidance is a minor remaining gap.
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 the schema already documents all six parameters including the unusual 20-row upstream minimum for page_size and the argued_after/argued_before date semantics. The description adds essentially nothing parameter-level beyond what the schema states, which is the expected baseline when the schema does the heavy lifting.
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?
States a specific verb and resource — 'Search appellate oral argument audio recordings' — and immediately characterizes the corpus ('largest public collection of oral argument audio'), which makes it clearly distinct from search_opinions and search_dockets. It does not explicitly say 'use X instead of Y' for the sibling search tools, so it stops just short of full sibling differentiation.
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?
Usage is only implied: the query matches case name and transcribed text, with optional court and date filtering. The one genuine routing hint is forwarding panel judge IDs to courtlistener_get_judge, which is a helpful follow-up workflow rather than a when-to-use rule. No exclusions or alternative-tool guidance are given.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
11 tool updates
- Changed
courtlistener_get_citations11 fields changed- changed
Input schema / properties / cursor / descriptionPrevious value: -"Pagination cursor from a previous response's next_cursor field."New value: +"Pagination cursor from next_cursor. For citing, a nonnegative safe decimal integer offset; for cited_by, an opaque upstream token." - changed
Input schema / properties / page_size / descriptionPrevious value: -"Number of results to request (default 20). For direction=\"cited_by\", CourtListener enforces a minimum of 20 results per page regardless of the value passed — you will always receive at least 20 results. direction=\"citing\" returns at most page_size (the cited-opinion list is sliced before querying) — fewer when the opinion cites fewer than page_size distinct opinions. Either direction costs three requests against the rate limit (a case with many opinion variants costs one more per extra variant page) — keep low for multi-hop traversal."New value: +"Positive requested size (default 20), bounded to 20. cited_by has an upstream minimum of 20; citing slices at most 20 cited IDs by the bounded size before filtering. Full upstream pages are preserved. Final or filtered pages can be smaller or empty; retain next_cursor to continue. page_sizing distinguishes requested, bounded and actual sizes. A normal call costs three requests plus extra variant pages." - changed
Input schema / properties / page_size / maximumPrevious value: -20New value: +9007199254740991 - changed
Output schema / anyOfPrevious value: -[ - { - "not": { - "required": [ - "error" - ] - }, - "required": [ - "source_cluster_id", - "source_case_name", - "direction", - "results", - "next_cursor", - "totalCount" - ] - }, - { - "required": [ - "error" - ] - } -]New value: +[ + { + "not": { + "required": [ + "error" + ] + }, + "required": [ + "source_cluster_id", + "source_case_name", + "direction", + "results", + "next_cursor" + ] + }, + { + "required": [ + "error" + ] + } +] - changed
Output schema / properties / error / properties / data / properties / reason / descriptionPrevious value: -"Machine-readable failure mode. Declared by this tool: `not_found`: Cluster ID does not exist in CourtListener. Both directions resolve the source cluster before searching, so a bad ID fails here rather than returning an empty network. `rate_limited`: 429 from CourtListener, or no request slot opened within the wait budget. `invalid_date`: filed_after is not a valid ISO 8601 calendar date. Other values are possible when a failure originates below the handler."New value: +"Machine-readable failure mode. Declared by this tool: `invalid_cursor`: A citing cursor is not a nonnegative safe decimal integer offset. `not_found`: Cluster ID does not exist in CourtListener. Both directions resolve the source cluster before searching, so a bad ID fails here rather than returning an empty network. `rate_limited`: 429 from CourtListener, or no request slot opened within the wait budget. `invalid_date`: filed_after is not a valid ISO 8601 calendar date. Other values are possible when a failure originates below the handler." - changed
Output schema / properties / error / properties / data / properties / reason / examplesPrevious value: -[ - "not_found", - "rate_limited", - "invalid_date" -]New value: +[ + "invalid_cursor", + "not_found", + "rate_limited", + "invalid_date" +] - added
Output schema / properties / observed_totalAdded value: +{ + "description": "Citation total observed from the fetched source variants; a lower bound when total_is_partial is true.", + "type": "number" +} - added
Output schema / properties / page_sizingAdded value: +{ + "additionalProperties": false, + "description": "Requested, bounded, and actual page sizes.", + "properties": { + "actual": { + "description": "Rows returned to the caller after any page-local filters.", + "type": "number" + }, + "bounded": { + "description": "Size sent upstream or used for the cited-ID slice.", + "type": "number" + }, + "requested": { + "description": "Caller-requested page size.", + "type": "number" + }, + "upstream": { + "description": "Upstream minimum, fixed page, or cited-ID slicing policy; final pages may contain fewer rows.", + "enum": [ + "minimum_20", + "fixed_20", + "cited_id_slice" + ], + "type": "string" + } + }, + "required": [ + "requested", + "bounded", + "actual", + "upstream" + ], + "type": "object" +} - added
Output schema / properties / source_variants_completionAdded value: +{ + "additionalProperties": false, + "description": "Completion of the source opinion-variant walk.", + "properties": { + "complete": { + "description": "True only when all source variants were fetched.", + "type": "boolean" + }, + "next_cursor": { + "description": "Remaining upstream variant cursor; null at the end.", + "type": [ + "string", + "null" + ] + } + }, + "required": [ + "complete", + "next_cursor" + ], + "type": "object" +} - changed
Output schema / properties / totalCount / descriptionPrevious value: -"Total citations in the requested direction. For \"cited_by\" it counts matching clusters with the court and filed_after filters applied. For \"citing\" it counts the distinct opinions this case cites, before any filter — so it exceeds what the filters make reachable, and runs higher than the result rows, which are clusters (several cited opinions in one case collapse to one row)."New value: +"Exact total for the fetched direction when source variants are complete; absent when total_is_partial is true. For cited_by this counts matching clusters after filters; for citing it counts distinct cited opinions before any filter, which can exceed the cluster rows." - added
Output schema / properties / total_is_partialAdded value: +{ + "description": "True when citation results and totals are based on an incomplete source-variant set.", + "type": "boolean" +}
- Changed
courtlistener_get_docket4 fields changed- changed
Input schema / properties / entries_page_size / maximumPrevious value: -50New value: +9007199254740991 - added
Output schema / properties / page_sizingAdded value: +{ + "additionalProperties": false, + "description": "Requested, bounded, and actual page sizes.", + "properties": { + "actual": { + "description": "Rows returned to the caller after any page-local filters.", + "type": "number" + }, + "bounded": { + "description": "Size sent upstream or used for the cited-ID slice.", + "type": "number" + }, + "requested": { + "description": "Caller-requested page size.", + "type": "number" + }, + "upstream": { + "description": "Upstream minimum, fixed page, or cited-ID slicing policy; final pages may contain fewer rows.", + "enum": [ + "minimum_20", + "fixed_20", + "cited_id_slice" + ], + "type": "string" + } + }, + "required": [ + "requested", + "bounded", + "actual", + "upstream" + ], + "type": "object" +} - changed
Output schema / properties / total_entries / descriptionPrevious value: -"Total number of docket entries available — may exceed the returned entries list."New value: +"Total number of docket entries available; null when upstream supplies no numeric total. May exceed the returned entries list." - changed
Output schema / properties / total_entries / typePrevious value: -"number"New value: +[ + "number", + "null" +]
- Changed
courtlistener_get_financial_disclosure26 fields changed- changed
Input schema / properties / categories / descriptionPrevious value: -"Line-item categories to return in full: investments, debts, positions, reimbursements, non_investment_incomes, spouse_incomes, agreements, gifts. Omit for all categories (or an outline if they overflow the inline budget). Also the re-call selector — after an outline response, re-call with the category names it lists."New value: +"Line-item categories to select. Omit for all. Oversized selections page; keep this selection unchanged while following cursor." - added
Input schema / properties / cursorAdded value: +{ + "description": "Retrieval next_cursor from the previous response. Repeat the original ID and sections/categories selection unchanged; omit to start.", + "maxLength": 1024, + "type": "string" +} - changed
Output schema / anyOfPrevious value: -[ - { - "not": { - "required": [ - "error" - ] - }, - "required": [ - "disclosure_id", - "person_id", - "year", - "report_type", - "page_count", - "has_been_extracted", - "is_amended", - "pdf_url", - "counts", - "kind" - ] - }, - { - "required": [ - "error" - ] - } -]New value: +[ + { + "not": { + "required": [ + "error" + ] + }, + "required": [ + "disclosure_id", + "person_id", + "year", + "page_count", + "has_been_extracted", + "is_amended", + "counts", + "kind" + ] + }, + { + "required": [ + "error" + ] + } +] - changed
Output schema / properties / agreements / items / descriptionPrevious value: -"A continuing agreement or arrangement (Part VIII)."New value: +"A continuing agreement or arrangement (Part VIII); omitted partial strings remain reachable through retrieval." - changed
Output schema / properties / agreements / items / requiredPrevious value: -[ - "id", - "date", - "parties_and_terms", - "redacted" -]New value: +[ + "id", + "redacted" +] - changed
Output schema / properties / debts / items / descriptionPrevious value: -"A debt or liability (Part VII)."New value: +"A debt or liability (Part VII); omitted partial strings remain reachable through retrieval." - changed
Output schema / properties / debts / items / requiredPrevious value: -[ - "id", - "creditor", - "description", - "value_range", - "redacted" -]New value: +[ + "id", + "redacted" +] - changed
Output schema / properties / error / properties / data / properties / reason / descriptionPrevious value: -"Machine-readable failure mode. Declared by this tool: `not_found`: Disclosure ID does not exist in CourtListener. `rate_limited`: 429 from CourtListener, or no request slot opened within the wait budget. Other values are possible when a failure originates below the handler."New value: +"Machine-readable failure mode. Declared by this tool: `invalid_cursor`: Retrieval cursor is malformed, out of range or belongs to another request. `stale_cursor`: The normalized selected source changed since the previous page. `not_found`: Disclosure ID does not exist in CourtListener. `rate_limited`: 429 from CourtListener, or no request slot opened within the wait budget. Other values are possible when a failure originates below the handler." - changed
Output schema / properties / error / properties / data / properties / reason / examplesPrevious value: -[ - "not_found", - "rate_limited" -]New value: +[ + "invalid_cursor", + "stale_cursor", + "not_found", + "rate_limited" +] - changed
Output schema / properties / gifts / items / descriptionPrevious value: -"A reported gift (Part VI)."New value: +"A reported gift (Part VI); omitted partial strings remain reachable through retrieval." - removed
Output schema / properties / gifts / items / requiredRemoved value: -[ - "description", - "source", - "value" -] - changed
Output schema / properties / investments / items / descriptionPrevious value: -"An investment holding (Part VII)."New value: +"An investment holding (Part VII); omitted partial strings remain reachable through retrieval." - changed
Output schema / properties / investments / items / requiredPrevious value: -[ - "id", - "description", - "income_type", - "income_range", - "value_range", - "value_method", - "transaction", - "transaction_date", - "transaction_value_range", - "transaction_gain_range", - "transaction_partner", - "redacted" -]New value: +[ + "id", + "redacted" +] - changed
Output schema / properties / kind / descriptionPrevious value: -"'full' returns the requested category rows; 'outline' lists each category as a retrievable section (by byte size) when the itemization overflows the inline budget. Filing metadata and counts are present either way."New value: +"'full' carries a small selected record; 'outline' pages the section catalog; 'page' carries typed rows and field-path text chunks. Filing identity and counts remain present." - changed
Output schema / properties / kind / enumPrevious value: -[ - "full", - "outline" -]New value: +[ + "full", + "outline", + "page" +] - changed
Output schema / properties / non_investment_incomes / items / descriptionPrevious value: -"The filer's non-investment income (Part II)."New value: +"The filer's non-investment income (Part II); omitted partial strings remain reachable through retrieval." - changed
Output schema / properties / non_investment_incomes / items / requiredPrevious value: -[ - "id", - "date", - "source_type", - "amount", - "redacted" -]New value: +[ + "id", + "redacted" +] - changed
Output schema / properties / positions / items / descriptionPrevious value: -"An outside position held by the filer (Part I)."New value: +"An outside position held by the filer (Part I); omitted partial strings remain reachable through retrieval." - changed
Output schema / properties / positions / items / requiredPrevious value: -[ - "id", - "position", - "organization", - "redacted" -]New value: +[ + "id", + "redacted" +] - changed
Output schema / properties / reimbursements / items / descriptionPrevious value: -"A travel/event reimbursement (Part IV)."New value: +"A travel/event reimbursement (Part IV); omitted partial strings remain reachable through retrieval." - changed
Output schema / properties / reimbursements / items / requiredPrevious value: -[ - "id", - "source", - "date", - "location", - "purpose", - "items", - "redacted" -]New value: +[ + "id", + "redacted" +] - added
Output schema / properties / retrievalAdded value: +{ + "additionalProperties": false, + "description": "Caller retrieval completion, separate from upstream source completion.", + "properties": { + "next_cursor": { + "description": "Continue with cursor and the same ID/selection; null when this fetched view is exhausted.", + "type": [ + "string", + "null" + ] + }, + "ranges": { + "description": "Absolute source coordinates; merge typed rows by index rather than appending duplicates.", + "items": { + "additionalProperties": false, + "description": "Source range.", + "properties": { + "end": { + "description": "Exclusive absolute end.", + "maximum": 9007199254740991, + "minimum": -9007199254740991, + "type": "integer" + }, + "path": { + "description": "JSON Pointer into the normalized unsliced selected view.", + "type": "string" + }, + "start": { + "description": "Inclusive absolute start.", + "maximum": 9007199254740991, + "minimum": -9007199254740991, + "type": "integer" + }, + "total": { + "description": "Length of the complete normalized collection or text field.", + "maximum": 9007199254740991, + "minimum": -9007199254740991, + "type": "integer" + }, + "unit": { + "description": "Coordinate unit.", + "enum": [ + "rows", + "code_points", + "sections" + ], + "type": "string" + } + }, + "required": [ + "path", + "unit", + "start", + "end", + "total" + ], + "type": "object" + }, + "type": "array" + }, + "text_chunks": { + "description": "Text omitted from partial rows/metadata, recoverable exactly using the matching ranges.", + "items": { + "additionalProperties": false, + "description": "Readable string slice.", + "properties": { + "path": { + "description": "JSON Pointer of the original string field or string-array element.", + "type": "string" + }, + "text": { + "description": "Unescaped normalized substring, matching its code_points range.", + "type": "string" + } + }, + "required": [ + "path", + "text" + ], + "type": "object" + }, + "type": "array" + } + }, + "required": [ + "next_cursor", + "ranges", + "text_chunks" + ], + "type": "object" +} - changed
Output schema / properties / retrieval_notice / descriptionPrevious value: -"How to re-call the tool for specific categories when the itemization overflows."New value: +"How to continue bounded retrieval using the unchanged ID and selection." - changed
Output schema / properties / sections / descriptionPrevious value: -"Retrievable categories, largest first — pass names to `categories` on a re-call."New value: +"Category catalog in declared order, with paged metadata fields. Follow retrieval.next_cursor to finish the catalog and retrieve data." - changed
Output schema / properties / spouse_incomes / items / descriptionPrevious value: -"The filer's spouse income (Part III)."New value: +"The filer's spouse income (Part III); omitted partial strings remain reachable through retrieval." - changed
Output schema / properties / spouse_incomes / items / requiredPrevious value: -[ - "id", - "source_type", - "date", - "redacted" -]New value: +[ + "id", + "redacted" +]
- Changed
courtlistener_get_opinion16 fields changed- added
Input schema / properties / cursorAdded value: +{ + "description": "Retrieval next_cursor from the previous response. Repeat the original ID and sections/categories selection unchanged; omit to start.", + "maxLength": 1024, + "type": "string" +} - changed
Input schema / properties / sections / descriptionPrevious value: -"Opinion variant identifiers to retrieve in full, from a prior outline response (e.g. [\"opinion_12345\"]). Omit to return all variants, or an outline if they overflow the inline byte budget."New value: +"Opinion variant identifiers to select (e.g. [\"opinion_12345\"]). Omit for all fetched variants. Oversized selections page; keep this selection unchanged while following cursor." - changed
Output schema / anyOfPrevious value: -[ - { - "not": { - "required": [ - "error" - ] - }, - "required": [ - "cluster_id", - "case_name", - "case_name_full", - "court", - "court_id", - "date_filed", - "docket_id", - "docket_number", - "judges", - "citations", - "cite_count", - "precedential_status", - "syllabus", - "posture", - "kind" - ] - }, - { - "required": [ - "error" - ] - } -]New value: +[ + { + "not": { + "required": [ + "error" + ] + }, + "required": [ + "cluster_id", + "docket_id", + "cite_count", + "kind" + ] + }, + { + "required": [ + "error" + ] + } +] - added
Output schema / properties / docket_enrichmentAdded value: +{ + "additionalProperties": false, + "description": "Linked-docket enrichment outcome, independent of opinion text availability.", + "properties": { + "error_code": { + "description": "Sanitized MCP error code when the lookup failed.", + "type": "number" + }, + "reason": { + "description": "Safe lookup failure category, without upstream error text.", + "enum": [ + "not_found", + "lookup_failed" + ], + "type": "string" + }, + "status": { + "description": "Outcome of the optional linked-docket lookup.", + "enum": [ + "not_linked", + "resolved", + "source_fields_absent", + "lookup_failed" + ], + "type": "string" + } + }, + "required": [ + "status" + ], + "type": "object" +} - changed
Output schema / properties / error / properties / data / properties / reason / descriptionPrevious value: -"Machine-readable failure mode. Declared by this tool: `not_found`: Cluster ID does not exist in CourtListener. `rate_limited`: 429 from CourtListener, or no request slot opened within the wait budget. `unknown_section`: A requested sections name matches no opinion variant in this cluster. Other values are possible when a failure originates below the handler."New value: +"Machine-readable failure mode. Declared by this tool: `invalid_cursor`: Retrieval cursor is malformed, out of range or belongs to another request. `stale_cursor`: The normalized selected source changed since the previous page. `not_found`: Cluster ID does not exist in CourtListener. `rate_limited`: 429 from CourtListener, or no request slot opened within the wait budget. `unknown_section`: A requested sections name matches no opinion variant in this cluster. Other values are possible when a failure originates below the handler." - changed
Output schema / properties / error / properties / data / properties / reason / examplesPrevious value: -[ - "not_found", - "rate_limited", - "unknown_section" -]New value: +[ + "invalid_cursor", + "stale_cursor", + "not_found", + "rate_limited", + "unknown_section" +] - changed
Output schema / properties / kind / descriptionPrevious value: -"'full' returns the opinion variants (all, or a selected subset); 'outline' lists each variant as a retrievable section (opinion_<id>) when the opinions overflow the inline byte budget. Cluster metadata is present either way."New value: +"'full' carries a small selected record; 'outline' pages the section catalog; 'page' carries typed rows and field-path text chunks. Bounded identity remains present throughout retrieval." - changed
Output schema / properties / kind / enumPrevious value: -[ - "full", - "outline" -]New value: +[ + "full", + "outline", + "page" +] - changed
Output schema / properties / opinions / descriptionPrevious value: -"All opinion variants within this cluster. Present in full mode; omitted in outline mode — re-call with sections:[\"opinion_<id>\"] to retrieve specific variants."New value: +"Fetched variants; variants_completion describes source coverage. Pages can contain partial typed variants; omitted text is recoverable through retrieval.text_chunks at original field paths." - changed
Output schema / properties / opinions / items / descriptionPrevious value: -"Individual opinion variant."New value: +"Individual opinion variant; omitted partial fields are recoverable through retrieval." - changed
Output schema / properties / opinions / items / properties / plain_text / descriptionPrevious value: -"Plain text version of the opinion; may be empty."New value: +"Supplied plain text preserved exactly, or readable text derived from source markup when absent; empty if neither exists." - changed
Output schema / properties / opinions / items / requiredPrevious value: -[ - "id", - "type", - "type_label", - "author_id", - "per_curiam", - "html_text", - "plain_text", - "cites", - "download_url" -]New value: +[ + "id", + "author_id", + "per_curiam" +] - added
Output schema / properties / retrievalAdded value: +{ + "additionalProperties": false, + "description": "Caller retrieval completion, separate from upstream source completion.", + "properties": { + "next_cursor": { + "description": "Continue with cursor and the same ID/selection; null when this fetched view is exhausted.", + "type": [ + "string", + "null" + ] + }, + "ranges": { + "description": "Absolute source coordinates; merge typed rows by index rather than appending duplicates.", + "items": { + "additionalProperties": false, + "description": "Source range.", + "properties": { + "end": { + "description": "Exclusive absolute end.", + "maximum": 9007199254740991, + "minimum": -9007199254740991, + "type": "integer" + }, + "path": { + "description": "JSON Pointer into the normalized unsliced selected view.", + "type": "string" + }, + "start": { + "description": "Inclusive absolute start.", + "maximum": 9007199254740991, + "minimum": -9007199254740991, + "type": "integer" + }, + "total": { + "description": "Length of the complete normalized collection or text field.", + "maximum": 9007199254740991, + "minimum": -9007199254740991, + "type": "integer" + }, + "unit": { + "description": "Coordinate unit.", + "enum": [ + "rows", + "code_points", + "sections" + ], + "type": "string" + } + }, + "required": [ + "path", + "unit", + "start", + "end", + "total" + ], + "type": "object" + }, + "type": "array" + }, + "text_chunks": { + "description": "Text omitted from partial rows/metadata, recoverable exactly using the matching ranges.", + "items": { + "additionalProperties": false, + "description": "Readable string slice.", + "properties": { + "path": { + "description": "JSON Pointer of the original string field or string-array element.", + "type": "string" + }, + "text": { + "description": "Unescaped normalized substring, matching its code_points range.", + "type": "string" + } + }, + "required": [ + "path", + "text" + ], + "type": "object" + }, + "type": "array" + } + }, + "required": [ + "next_cursor", + "ranges", + "text_chunks" + ], + "type": "object" +} - changed
Output schema / properties / retrieval_notice / descriptionPrevious value: -"How to re-call the tool for specific opinion variants when the opinions overflow."New value: +"How to continue bounded retrieval using the unchanged ID and selection." - changed
Output schema / properties / sections / descriptionPrevious value: -"Retrievable opinion variants, largest first — pass names to `sections` on a re-call."New value: +"Section catalog in source order, including paged metadata. Only opinion_<id> names select variants; follow retrieval.next_cursor to finish the catalog and retrieve data." - added
Output schema / properties / variants_completionAdded value: +{ + "additionalProperties": false, + "description": "Source-walk completion. An oversized upstream next_cursor is omitted on partial responses and recovered at /variants_completion/next_cursor through retrieval.text_chunks.", + "properties": { + "complete": { + "description": "True only when all source variants were fetched.", + "type": "boolean" + }, + "next_cursor": { + "description": "Remaining upstream variant cursor; null at the end.", + "type": [ + "string", + "null" + ] + } + }, + "required": [ + "complete" + ], + "type": "object" +}
- Changed
courtlistener_get_oral_argument10 fields changed- added
Input schema / properties / cursorAdded value: +{ + "description": "Retrieval next_cursor from the previous response. Repeat the original ID and sections/categories selection unchanged; omit to start.", + "maxLength": 1024, + "type": "string" +} - changed
Input schema / properties / sections / descriptionPrevious value: -"Section identifiers to retrieve, from a prior outline response — [\"transcript\"] is the only one that adds anything, since every other field is returned regardless. A selection that omits \"transcript\" therefore returns the record without it. Omit this argument entirely for the whole record, or the record minus an oversized transcript."New value: +"Selected record fields. Metadata is always selected; a nonempty selection omitting transcript excludes it. Omit for the whole record. Oversized selections page; keep this selection unchanged while following cursor." - changed
Output schema / properties / error / properties / data / properties / reason / descriptionPrevious value: -"Machine-readable failure mode. Declared by this tool: `not_found`: Audio ID does not exist in CourtListener. `rate_limited`: 429 from CourtListener, or no request slot opened within the wait budget. `unknown_section`: A requested sections name is not a field of the oral argument record. Other values are possible when a failure originates below the handler."New value: +"Machine-readable failure mode. Declared by this tool: `invalid_cursor`: Retrieval cursor is malformed, out of range or belongs to another request. `stale_cursor`: The normalized selected source changed since the previous page. `not_found`: Audio ID does not exist in CourtListener. `rate_limited`: 429 from CourtListener, or no request slot opened within the wait budget. `unknown_section`: A requested sections name is not a field of the oral argument record. Other values are possible when a failure originates below the handler." - changed
Output schema / properties / error / properties / data / properties / reason / examplesPrevious value: -[ - "not_found", - "rate_limited", - "unknown_section" -]New value: +[ + "invalid_cursor", + "stale_cursor", + "not_found", + "rate_limited", + "unknown_section" +] - changed
Output schema / properties / kind / descriptionPrevious value: -"'full' carries the transcript inline; 'outline' withholds it and lists it as a retrievable section because it overflows the inline byte budget. Every other field of the record is present either way."New value: +"'full' carries a small selected record; 'outline' pages the section catalog; 'page' carries fields and text chunks. Bounded identity remains present throughout retrieval." - changed
Output schema / properties / kind / enumPrevious value: -[ - "full", - "outline" -]New value: +[ + "full", + "outline", + "page" +] - added
Output schema / properties / retrievalAdded value: +{ + "additionalProperties": false, + "description": "Caller retrieval completion, separate from upstream source completion.", + "properties": { + "next_cursor": { + "description": "Continue with cursor and the same ID/selection; null when this fetched view is exhausted.", + "type": [ + "string", + "null" + ] + }, + "ranges": { + "description": "Absolute source coordinates; merge typed rows by index rather than appending duplicates.", + "items": { + "additionalProperties": false, + "description": "Source range.", + "properties": { + "end": { + "description": "Exclusive absolute end.", + "maximum": 9007199254740991, + "minimum": -9007199254740991, + "type": "integer" + }, + "path": { + "description": "JSON Pointer into the normalized unsliced selected view.", + "type": "string" + }, + "start": { + "description": "Inclusive absolute start.", + "maximum": 9007199254740991, + "minimum": -9007199254740991, + "type": "integer" + }, + "total": { + "description": "Length of the complete normalized collection or text field.", + "maximum": 9007199254740991, + "minimum": -9007199254740991, + "type": "integer" + }, + "unit": { + "description": "Coordinate unit.", + "enum": [ + "rows", + "code_points", + "sections" + ], + "type": "string" + } + }, + "required": [ + "path", + "unit", + "start", + "end", + "total" + ], + "type": "object" + }, + "type": "array" + }, + "text_chunks": { + "description": "Text omitted from partial rows/metadata, recoverable exactly using the matching ranges.", + "items": { + "additionalProperties": false, + "description": "Readable string slice.", + "properties": { + "path": { + "description": "JSON Pointer of the original string field or string-array element.", + "type": "string" + }, + "text": { + "description": "Unescaped normalized substring, matching its code_points range.", + "type": "string" + } + }, + "required": [ + "path", + "text" + ], + "type": "object" + }, + "type": "array" + } + }, + "required": [ + "next_cursor", + "ranges", + "text_chunks" + ], + "type": "object" +} - changed
Output schema / properties / retrieval_notice / descriptionPrevious value: -"How to re-call the tool for the transcript when it overflows the inline budget."New value: +"How to continue bounded retrieval using the unchanged ID and selection." - changed
Output schema / properties / sections / descriptionPrevious value: -"Sections withheld from this response — only ever `transcript`; pass its name to `sections` on a re-call. Absent when nothing was withheld."New value: +"Section catalog: transcript and paged metadata fields. Follow retrieval.next_cursor to finish the catalog and retrieve data." - changed
Output schema / properties / transcript / descriptionPrevious value: -"Speech-to-text transcript; empty string if transcription has not completed. The only field an outline response withholds — re-call with sections:[\"transcript\"] to retrieve it."New value: +"Speech-to-text transcript; empty if transcription has not completed. Oversized text is recovered through retrieval.text_chunks at /transcript."
- Changed
courtlistener_get_parties6 fields changed- changed
Input schema / properties / page_size / descriptionPrevious value: -"Requested number of parties per page (1–10). CourtListener paginates this endpoint at a fixed size and does not honor the requested value, so a page can come back larger than asked for."New value: +"Positive requested party page size (default 10), bounded to 10 before retrieval. CourtListener uses fixed 20-row pages and ignores this request; final pages can be smaller. page_sizing reports requested, bounded and actual sizes." - changed
Input schema / properties / page_size / maximumPrevious value: -10New value: +9007199254740991 - added
Output schema / properties / attorney_resolutionAdded value: +{ + "additionalProperties": false, + "description": "Attorney lookup completeness; no additional automatic requests are made.", + "properties": { + "next_cursor": { + "description": "Remaining attorney-roster cursor; null when exhausted.", + "type": [ + "string", + "null" + ] + }, + "status": { + "description": "Resolved all needed IDs, exhausted roster with misses, or stopped at the page cap.", + "enum": [ + "resolved", + "exhausted", + "capped" + ], + "type": "string" + }, + "unresolved_ids": { + "description": "Attorney IDs still unresolved on this parties page.", + "items": { + "type": "number" + }, + "type": "array" + } + }, + "required": [ + "status", + "unresolved_ids", + "next_cursor" + ], + "type": "object" +} - changed
Output schema / properties / error / properties / data / properties / reason / descriptionPrevious value: -"Machine-readable failure mode. Declared by this tool: `not_found`: Docket ID does not exist in CourtListener or has no RECAP party data. `rate_limited`: 429 from CourtListener, or no request slot opened within the wait budget. Each call to this tool makes at least two upstream requests. Other values are possible when a failure originates below the handler."New value: +"Machine-readable failure mode. Declared by this tool: `not_found`: Docket ID does not exist in CourtListener or has no RECAP party data. `rate_limited`: 429 from CourtListener, or no request slot opened before any attorney roster page completed. Other values are possible when a failure originates below the handler." - added
Output schema / properties / page_sizingAdded value: +{ + "additionalProperties": false, + "description": "Requested, bounded, and actual page sizes.", + "properties": { + "actual": { + "description": "Rows returned to the caller after any page-local filters.", + "type": "number" + }, + "bounded": { + "description": "Size sent upstream or used for the cited-ID slice.", + "type": "number" + }, + "requested": { + "description": "Caller-requested page size.", + "type": "number" + }, + "upstream": { + "description": "Upstream minimum, fixed page, or cited-ID slicing policy; final pages may contain fewer rows.", + "enum": [ + "minimum_20", + "fixed_20", + "cited_id_slice" + ], + "type": "string" + } + }, + "required": [ + "requested", + "bounded", + "actual", + "upstream" + ], + "type": "object" +} - added
Output schema / properties / parties / items / properties / attorneys / items / properties / resolutionAdded value: +{ + "description": "Whether detail was resolved (possibly with empty source fields), absent from an exhausted roster, or unknown after the cap.", + "enum": [ + "resolved", + "not_found", + "not_fetched" + ], + "type": "string" +}
- Changed
courtlistener_search_dockets3 fields changed- changed
Input schema / properties / page_size / descriptionPrevious value: -"Number of results to request (default 20). CourtListener search enforces a minimum of 20 results per page regardless of the value passed — you will always receive at least 20 results."New value: +"Positive requested page size (default 20), bounded to 20. Upstream search has a 20-row minimum; empty and final pages can be smaller. Full pages and continuation are preserved; page_sizing reports actual sizes." - changed
Input schema / properties / page_size / maximumPrevious value: -20New value: +9007199254740991 - added
Output schema / properties / page_sizingAdded value: +{ + "additionalProperties": false, + "description": "Requested, bounded, and actual page sizes.", + "properties": { + "actual": { + "description": "Rows returned to the caller after any page-local filters.", + "type": "number" + }, + "bounded": { + "description": "Size sent upstream or used for the cited-ID slice.", + "type": "number" + }, + "requested": { + "description": "Caller-requested page size.", + "type": "number" + }, + "upstream": { + "description": "Upstream minimum, fixed page, or cited-ID slicing policy; final pages may contain fewer rows.", + "enum": [ + "minimum_20", + "fixed_20", + "cited_id_slice" + ], + "type": "string" + } + }, + "required": [ + "requested", + "bounded", + "actual", + "upstream" + ], + "type": "object" +}
- Changed
courtlistener_search_financial_disclosures3 fields changed- changed
Input schema / properties / page_size / descriptionPrevious value: -"Number of filings to request (default 20). CourtListener enforces a minimum of 20 results per page regardless of the value passed — you will always receive at least 20 filings."New value: +"Positive requested page size (default 20), bounded to 20. Upstream has a minimum of 20; final pages and page-local year filtering can return fewer. Full fetched pages and continuation are preserved; page_sizing reports returned sizes." - changed
Input schema / properties / page_size / maximumPrevious value: -20New value: +9007199254740991 - added
Output schema / properties / page_sizingAdded value: +{ + "additionalProperties": false, + "description": "Requested, bounded, and actual page sizes.", + "properties": { + "actual": { + "description": "Rows returned to the caller after any page-local filters.", + "type": "number" + }, + "bounded": { + "description": "Size sent upstream or used for the cited-ID slice.", + "type": "number" + }, + "requested": { + "description": "Caller-requested page size.", + "type": "number" + }, + "upstream": { + "description": "Upstream minimum, fixed page, or cited-ID slicing policy; final pages may contain fewer rows.", + "enum": [ + "minimum_20", + "fixed_20", + "cited_id_slice" + ], + "type": "string" + } + }, + "required": [ + "requested", + "bounded", + "actual", + "upstream" + ], + "type": "object" +}
- Changed
courtlistener_search_judges3 fields changed- changed
Input schema / properties / page_size / descriptionPrevious value: -"Number of results to request (default 20). CourtListener search enforces a minimum of 20 results per page regardless of the value passed."New value: +"Positive requested page size (default 20), bounded to 20. Upstream search has a 20-row minimum; empty and final pages can be smaller. Full pages and continuation are preserved; page_sizing reports actual sizes." - changed
Input schema / properties / page_size / maximumPrevious value: -20New value: +9007199254740991 - added
Output schema / properties / page_sizingAdded value: +{ + "additionalProperties": false, + "description": "Requested, bounded, and actual page sizes.", + "properties": { + "actual": { + "description": "Rows returned to the caller after any page-local filters.", + "type": "number" + }, + "bounded": { + "description": "Size sent upstream or used for the cited-ID slice.", + "type": "number" + }, + "requested": { + "description": "Caller-requested page size.", + "type": "number" + }, + "upstream": { + "description": "Upstream minimum, fixed page, or cited-ID slicing policy; final pages may contain fewer rows.", + "enum": [ + "minimum_20", + "fixed_20", + "cited_id_slice" + ], + "type": "string" + } + }, + "required": [ + "requested", + "bounded", + "actual", + "upstream" + ], + "type": "object" +}
- Changed
courtlistener_search_opinions4 fields changed- changed
Input schema / properties / page_size / descriptionPrevious value: -"Number of results to request (default 20). CourtListener search enforces a minimum of 20 results per page regardless of the value passed — you will always receive at least 20 results. Each search costs one request against the rate limit."New value: +"Positive requested page size (default 20), bounded to 20 before retrieval. Upstream search has a 20-row minimum; empty and final pages can be smaller. Full upstream pages and continuation are preserved; page_sizing reports requested, bounded and actual sizes." - changed
Input schema / properties / page_size / maximumPrevious value: -20New value: +9007199254740991 - changed
Input schema / properties / status / descriptionPrevious value: -"Opinion publication status. \"Published\": precedential. \"Unpublished\": not citable as precedent in most jurisdictions. \"Errata\": corrections. \"Separate\": separate opinion filed outside main cluster. \"In-chambers\": single-justice order. \"Relating-to\": companion or related-case order. Omit to search all statuses."New value: +"Opinion publication status. \"Published\": precedential. \"Unpublished\": not citable as precedent in most jurisdictions. \"Errata\": corrections. \"Separate\": separate opinion filed outside main cluster. \"In-chambers\": single-justice order. \"Relating-to\": companion or related-case order. Omit to use CourtListener’s Published default." - added
Output schema / properties / page_sizingAdded value: +{ + "additionalProperties": false, + "description": "Requested, bounded, and actual page sizes.", + "properties": { + "actual": { + "description": "Rows returned to the caller after any page-local filters.", + "type": "number" + }, + "bounded": { + "description": "Size sent upstream or used for the cited-ID slice.", + "type": "number" + }, + "requested": { + "description": "Caller-requested page size.", + "type": "number" + }, + "upstream": { + "description": "Upstream minimum, fixed page, or cited-ID slicing policy; final pages may contain fewer rows.", + "enum": [ + "minimum_20", + "fixed_20", + "cited_id_slice" + ], + "type": "string" + } + }, + "required": [ + "requested", + "bounded", + "actual", + "upstream" + ], + "type": "object" +}
- Changed
courtlistener_search_oral_arguments3 fields changed- changed
Input schema / properties / page_size / descriptionPrevious value: -"Number of results to request (default 20). CourtListener search enforces a minimum of 20 results per page regardless of the value passed."New value: +"Positive requested page size (default 20), bounded to 20. Upstream search has a 20-row minimum; empty and final pages can be smaller. Full pages and continuation are preserved; page_sizing reports actual sizes." - changed
Input schema / properties / page_size / maximumPrevious value: -20New value: +9007199254740991 - added
Output schema / properties / page_sizingAdded value: +{ + "additionalProperties": false, + "description": "Requested, bounded, and actual page sizes.", + "properties": { + "actual": { + "description": "Rows returned to the caller after any page-local filters.", + "type": "number" + }, + "bounded": { + "description": "Size sent upstream or used for the cited-ID slice.", + "type": "number" + }, + "requested": { + "description": "Caller-requested page size.", + "type": "number" + }, + "upstream": { + "description": "Upstream minimum, fixed page, or cited-ID slicing policy; final pages may contain fewer rows.", + "enum": [ + "minimum_20", + "fixed_20", + "cited_id_slice" + ], + "type": "string" + } + }, + "required": [ + "requested", + "bounded", + "actual", + "upstream" + ], + "type": "object" +}
4 tool updates
- Changed
courtlistener_search_dockets2 fields changed- changed
Output schema / properties / error / properties / data / properties / reason / descriptionPrevious value: -"Machine-readable failure mode. Declared by this tool: `rate_limited`: 429 from CourtListener, or no request slot opened within the wait budget. `empty_query`: q is empty or whitespace-only after trimming — no request is sent. `invalid_date`: filed_after or filed_before is not a valid ISO 8601 calendar date. Other values are possible when a failure originates below the handler."New value: +"Machine-readable failure mode. Declared by this tool: `invalid_query`: CourtListener rejects caller-authored query or filter syntax with a recognized diagnostic. `rate_limited`: 429 from CourtListener, or no request slot opened within the wait budget. `empty_query`: q is empty or whitespace-only after trimming — no request is sent. `invalid_date`: filed_after or filed_before is not a valid ISO 8601 calendar date. Other values are possible when a failure originates below the handler." - changed
Output schema / properties / error / properties / data / properties / reason / examplesPrevious value: -[ - "rate_limited", - "empty_query", - "invalid_date" -]New value: +[ + "invalid_query", + "rate_limited", + "empty_query", + "invalid_date" +]
- Changed
courtlistener_search_judges2 fields changed- changed
Output schema / properties / error / properties / data / properties / reason / descriptionPrevious value: -"Machine-readable failure mode. Declared by this tool: `rate_limited`: 429 from CourtListener, or no request slot opened within the wait budget. `empty_query`: q is empty or whitespace-only after trimming — no request is sent. Other values are possible when a failure originates below the handler."New value: +"Machine-readable failure mode. Declared by this tool: `invalid_query`: CourtListener rejects caller-authored query or filter syntax with a recognized diagnostic. `rate_limited`: 429 from CourtListener, or no request slot opened within the wait budget. `empty_query`: q is empty or whitespace-only after trimming — no request is sent. Other values are possible when a failure originates below the handler." - changed
Output schema / properties / error / properties / data / properties / reason / examplesPrevious value: -[ - "rate_limited", - "empty_query" -]New value: +[ + "invalid_query", + "rate_limited", + "empty_query" +]
- Changed
courtlistener_search_opinions2 fields changed- changed
Output schema / properties / error / properties / data / properties / reason / descriptionPrevious value: -"Machine-readable failure mode. Declared by this tool: `rate_limited`: 429 from CourtListener, or no request slot opened within the wait budget. `empty_query`: q is empty or whitespace-only after trimming — no request is sent. `invalid_date`: filed_after or filed_before is not a valid ISO 8601 calendar date. Other values are possible when a failure originates below the handler."New value: +"Machine-readable failure mode. Declared by this tool: `invalid_query`: CourtListener rejects caller-authored query or filter syntax with a recognized diagnostic. `rate_limited`: 429 from CourtListener, or no request slot opened within the wait budget. `empty_query`: q is empty or whitespace-only after trimming — no request is sent. `invalid_date`: filed_after or filed_before is not a valid ISO 8601 calendar date. Other values are possible when a failure originates below the handler." - changed
Output schema / properties / error / properties / data / properties / reason / examplesPrevious value: -[ - "rate_limited", - "empty_query", - "invalid_date" -]New value: +[ + "invalid_query", + "rate_limited", + "empty_query", + "invalid_date" +]
- Changed
courtlistener_search_oral_arguments2 fields changed- changed
Output schema / properties / error / properties / data / properties / reason / descriptionPrevious value: -"Machine-readable failure mode. Declared by this tool: `rate_limited`: 429 from CourtListener, or no request slot opened within the wait budget. `empty_query`: q is empty or whitespace-only after trimming — no request is sent. `invalid_date`: argued_after or argued_before is not a valid ISO 8601 calendar date. Other values are possible when a failure originates below the handler."New value: +"Machine-readable failure mode. Declared by this tool: `invalid_query`: CourtListener rejects caller-authored query or filter syntax with a recognized diagnostic. `rate_limited`: 429 from CourtListener, or no request slot opened within the wait budget. `empty_query`: q is empty or whitespace-only after trimming — no request is sent. `invalid_date`: argued_after or argued_before is not a valid ISO 8601 calendar date. Other values are possible when a failure originates below the handler." - changed
Output schema / properties / error / properties / data / properties / reason / examplesPrevious value: -[ - "rate_limited", - "empty_query", - "invalid_date" -]New value: +[ + "invalid_query", + "rate_limited", + "empty_query", + "invalid_date" +]
14 tool updates
- Changed
courtlistener_get_citations3 fields changed- changed
Output schema / properties / error / properties / data / properties / reason / descriptionPrevious value: -"Machine-readable failure mode. Declared by this tool: `not_found`: Cluster ID does not exist in CourtListener. Both directions resolve the source cluster before searching, so a bad ID fails here rather than returning an empty network. `rate_limited`: 429 response from CourtListener. `invalid_date`: filed_after is not a valid ISO 8601 calendar date. Other values are possible when a failure originates below the handler."New value: +"Machine-readable failure mode. Declared by this tool: `not_found`: Cluster ID does not exist in CourtListener. Both directions resolve the source cluster before searching, so a bad ID fails here rather than returning an empty network. `rate_limited`: 429 from CourtListener, or no request slot opened within the wait budget. `invalid_date`: filed_after is not a valid ISO 8601 calendar date. Other values are possible when a failure originates below the handler." - removed
Output schema / properties / next_cursor / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / next_cursor / typeAdded value: +[ + "string", + "null" +]
- Changed
courtlistener_get_docket21 fields changed- removed
Output schema / properties / assigned_to / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / assigned_to / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / date_terminated / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / date_terminated / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / entries / items / properties / documents / items / properties / attachment_number / anyOfRemoved value: -[ - { - "type": "number" - }, - { - "type": "null" - } -] - added
Output schema / properties / entries / items / properties / documents / items / properties / attachment_number / typeAdded value: +[ + "number", + "null" +] - removed
Output schema / properties / entries / items / properties / documents / items / properties / document_number / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / entries / items / properties / documents / items / properties / document_number / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / entries / items / properties / documents / items / properties / filepath_local / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / entries / items / properties / documents / items / properties / filepath_local / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / entries / items / properties / documents / items / properties / page_count / anyOfRemoved value: -[ - { - "type": "number" - }, - { - "type": "null" - } -] - added
Output schema / properties / entries / items / properties / documents / items / properties / page_count / typeAdded value: +[ + "number", + "null" +] - removed
Output schema / properties / entries / items / properties / entry_number / anyOfRemoved value: -[ - { - "type": "number" - }, - { - "type": "null" - } -] - added
Output schema / properties / entries / items / properties / entry_number / typeAdded value: +[ + "number", + "null" +] - changed
Output schema / properties / error / properties / data / properties / reason / descriptionPrevious value: -"Machine-readable failure mode. Declared by this tool: `not_found`: Docket ID does not exist in CourtListener. `rate_limited`: 429 response from CourtListener. Other values are possible when a failure originates below the handler."New value: +"Machine-readable failure mode. Declared by this tool: `not_found`: Docket ID does not exist in CourtListener. `rate_limited`: 429 from CourtListener, or no request slot opened within the wait budget. Other values are possible when a failure originates below the handler." - removed
Output schema / properties / next_cursor / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / next_cursor / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / pacer_case_id / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / pacer_case_id / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / referred_to / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / referred_to / typeAdded value: +[ + "string", + "null" +]
- Changed
courtlistener_get_financial_disclosure7 fields changed- changed
Output schema / properties / error / properties / data / properties / reason / descriptionPrevious value: -"Machine-readable failure mode. Declared by this tool: `not_found`: Disclosure ID does not exist in CourtListener. `rate_limited`: 429 response from CourtListener. Other values are possible when a failure originates below the handler."New value: +"Machine-readable failure mode. Declared by this tool: `not_found`: Disclosure ID does not exist in CourtListener. `rate_limited`: 429 from CourtListener, or no request slot opened within the wait budget. Other values are possible when a failure originates below the handler." - removed
Output schema / properties / page_count / anyOfRemoved value: -[ - { - "type": "number" - }, - { - "type": "null" - } -] - added
Output schema / properties / page_count / typeAdded value: +[ + "number", + "null" +] - removed
Output schema / properties / pdf_url / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / pdf_url / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / person_id / anyOfRemoved value: -[ - { - "type": "number" - }, - { - "type": "null" - } -] - added
Output schema / properties / person_id / typeAdded value: +[ + "number", + "null" +]
- Changed
courtlistener_get_judge45 fields changed- removed
Output schema / properties / dob / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / dob / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / dob_city / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / dob_city / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / dob_granularity / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / dob_granularity / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / dob_state / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / dob_state / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / dod / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / dod / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / dod_granularity / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / dod_granularity / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / education / items / properties / degree / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / education / items / properties / degree / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / education / items / properties / degree_label / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / education / items / properties / degree_label / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / education / items / properties / year / anyOfRemoved value: -[ - { - "type": "number" - }, - { - "type": "null" - } -] - added
Output schema / properties / education / items / properties / year / typeAdded value: +[ + "number", + "null" +] - changed
Output schema / properties / error / properties / data / properties / reason / descriptionPrevious value: -"Machine-readable failure mode. Declared by this tool: `not_found`: Person ID does not exist in CourtListener. `rate_limited`: 429 response from CourtListener. Other values are possible when a failure originates below the handler."New value: +"Machine-readable failure mode. Declared by this tool: `not_found`: Person ID does not exist in CourtListener. `rate_limited`: 429 from CourtListener, or no request slot opened within the wait budget. Other values are possible when a failure originates below the handler." - removed
Output schema / properties / fjc_id / anyOfRemoved value: -[ - { - "type": "number" - }, - { - "type": "null" - } -] - added
Output schema / properties / fjc_id / typeAdded value: +[ + "number", + "null" +] - removed
Output schema / properties / political_affiliations / items / properties / date_end / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / political_affiliations / items / properties / date_end / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / political_affiliations / items / properties / date_start / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / political_affiliations / items / properties / date_start / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / positions / items / properties / appointer / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / positions / items / properties / appointer / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / positions / items / properties / date_confirmation / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / positions / items / properties / date_confirmation / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / positions / items / properties / date_nominated / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / positions / items / properties / date_nominated / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / positions / items / properties / date_start / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / positions / items / properties / date_start / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / positions / items / properties / date_start_granularity / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / positions / items / properties / date_start_granularity / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / positions / items / properties / date_termination / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / positions / items / properties / date_termination / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / positions / items / properties / date_termination_granularity / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / positions / items / properties / date_termination_granularity / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / positions / items / properties / nomination_process / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / positions / items / properties / nomination_process / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / positions / items / properties / termination_reason / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / positions / items / properties / termination_reason / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / positions / items / properties / termination_reason_label / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / positions / items / properties / termination_reason_label / typeAdded value: +[ + "string", + "null" +]
- Changed
courtlistener_get_opinion5 fields changed- changed
Output schema / properties / error / properties / data / properties / reason / descriptionPrevious value: -"Machine-readable failure mode. Declared by this tool: `not_found`: Cluster ID does not exist in CourtListener. `rate_limited`: 429 response from CourtListener. `unknown_section`: A requested sections name matches no opinion variant in this cluster. Other values are possible when a failure originates below the handler."New value: +"Machine-readable failure mode. Declared by this tool: `not_found`: Cluster ID does not exist in CourtListener. `rate_limited`: 429 from CourtListener, or no request slot opened within the wait budget. `unknown_section`: A requested sections name matches no opinion variant in this cluster. Other values are possible when a failure originates below the handler." - removed
Output schema / properties / opinions / items / properties / author_id / anyOfRemoved value: -[ - { - "type": "number" - }, - { - "type": "null" - } -] - added
Output schema / properties / opinions / items / properties / author_id / typeAdded value: +[ + "number", + "null" +] - removed
Output schema / properties / opinions / items / properties / download_url / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / opinions / items / properties / download_url / typeAdded value: +[ + "string", + "null" +]
- Changed
courtlistener_get_oral_argument3 fields changed- removed
Output schema / properties / download_url / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / download_url / typeAdded value: +[ + "string", + "null" +] - changed
Output schema / properties / error / properties / data / properties / reason / descriptionPrevious value: -"Machine-readable failure mode. Declared by this tool: `not_found`: Audio ID does not exist in CourtListener. `rate_limited`: 429 response from CourtListener. `unknown_section`: A requested sections name is not a field of the oral argument record. Other values are possible when a failure originates below the handler."New value: +"Machine-readable failure mode. Declared by this tool: `not_found`: Audio ID does not exist in CourtListener. `rate_limited`: 429 from CourtListener, or no request slot opened within the wait budget. `unknown_section`: A requested sections name is not a field of the oral argument record. Other values are possible when a failure originates below the handler."
- Changed
courtlistener_get_parties11 fields changed- changed
Output schema / properties / error / properties / data / properties / reason / descriptionPrevious value: -"Machine-readable failure mode. Declared by this tool: `not_found`: Docket ID does not exist in CourtListener or has no RECAP party data. `rate_limited`: 429 response from CourtListener. Each call to this tool makes at least two upstream requests. Other values are possible when a failure originates below the handler."New value: +"Machine-readable failure mode. Declared by this tool: `not_found`: Docket ID does not exist in CourtListener or has no RECAP party data. `rate_limited`: 429 from CourtListener, or no request slot opened within the wait budget. Each call to this tool makes at least two upstream requests. Other values are possible when a failure originates below the handler." - removed
Output schema / properties / next_cursor / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / next_cursor / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / parties / items / properties / attorneys / items / properties / date_action / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / parties / items / properties / attorneys / items / properties / date_action / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / parties / items / properties / attorneys / items / properties / role_code / anyOfRemoved value: -[ - { - "type": "number" - }, - { - "type": "null" - } -] - added
Output schema / properties / parties / items / properties / attorneys / items / properties / role_code / typeAdded value: +[ + "number", + "null" +] - removed
Output schema / properties / parties / items / properties / role / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / parties / items / properties / role / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / total_parties / anyOfRemoved value: -[ - { - "type": "number" - }, - { - "type": "null" - } -] - added
Output schema / properties / total_parties / typeAdded value: +[ + "number", + "null" +]
- Changed
courtlistener_lookup_citation21 fields changed- changed
Output schema / properties / error / properties / data / properties / reason / descriptionPrevious value: -"Machine-readable failure mode. Declared by this tool: `not_found`: CourtListener could not parse any citation out of the submitted text. A citation that parses but matches nothing is a result with status 404, not this error. `rate_limited`: 429 response from CourtListener. `empty_citation`: citation is empty or whitespace-only after trimming — no request is sent. `citation_too_long`: citation exceeds the 64000-character ceiling CourtListener accepts — no request is sent. Other values are possible when a failure originates below the handler."New value: +"Machine-readable failure mode. Declared by this tool: `not_found`: CourtListener could not parse any citation out of the submitted text. A citation that parses but matches nothing is a result with status 404, not this error. `rate_limited`: 429 from CourtListener, or no request slot opened within the wait budget. `empty_citation`: citation is empty or whitespace-only after trimming — no request is sent. `citation_too_long`: citation exceeds the 64000-character ceiling CourtListener accepts — no request is sent. Other values are possible when a failure originates below the handler." - removed
Output schema / properties / matches / items / properties / clusters / items / properties / case_name / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / matches / items / properties / clusters / items / properties / case_name / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / matches / items / properties / clusters / items / properties / cite_count / anyOfRemoved value: -[ - { - "type": "number" - }, - { - "type": "null" - } -] - added
Output schema / properties / matches / items / properties / clusters / items / properties / cite_count / typeAdded value: +[ + "number", + "null" +] - removed
Output schema / properties / matches / items / properties / clusters / items / properties / cluster_id / anyOfRemoved value: -[ - { - "type": "number" - }, - { - "type": "null" - } -] - added
Output schema / properties / matches / items / properties / clusters / items / properties / cluster_id / typeAdded value: +[ + "number", + "null" +] - removed
Output schema / properties / matches / items / properties / clusters / items / properties / court / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / matches / items / properties / clusters / items / properties / court / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / matches / items / properties / clusters / items / properties / court_id / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / matches / items / properties / clusters / items / properties / court_id / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / matches / items / properties / clusters / items / properties / date_filed / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / matches / items / properties / clusters / items / properties / date_filed / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / matches / items / properties / clusters / items / properties / docket_id / anyOfRemoved value: -[ - { - "type": "number" - }, - { - "type": "null" - } -] - added
Output schema / properties / matches / items / properties / clusters / items / properties / docket_id / typeAdded value: +[ + "number", + "null" +] - removed
Output schema / properties / matches / items / properties / clusters / items / properties / judges / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / matches / items / properties / clusters / items / properties / judges / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / matches / items / properties / clusters / items / properties / precedential_status / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / matches / items / properties / clusters / items / properties / precedential_status / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / matches / items / properties / normalized_citation / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / matches / items / properties / normalized_citation / typeAdded value: +[ + "string", + "null" +]
- Changed
courtlistener_lookup_courts3 fields changed- changed
Output schema / properties / error / properties / data / properties / reason / descriptionPrevious value: -"Machine-readable failure mode. Declared by this tool: `rate_limited`: 429 response from CourtListener. Other values are possible when a failure originates below the handler."New value: +"Machine-readable failure mode. Declared by this tool: `rate_limited`: 429 from CourtListener, or no request slot opened within the wait budget. Other values are possible when a failure originates below the handler." - removed
Output schema / properties / next_cursor / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / next_cursor / typeAdded value: +[ + "string", + "null" +]
- Changed
courtlistener_search_dockets19 fields changed- changed
Output schema / properties / error / properties / data / properties / reason / descriptionPrevious value: -"Machine-readable failure mode. Declared by this tool: `rate_limited`: 429 response from CourtListener. `empty_query`: q is empty or whitespace-only after trimming — no request is sent. `invalid_date`: filed_after or filed_before is not a valid ISO 8601 calendar date. Other values are possible when a failure originates below the handler."New value: +"Machine-readable failure mode. Declared by this tool: `rate_limited`: 429 from CourtListener, or no request slot opened within the wait budget. `empty_query`: q is empty or whitespace-only after trimming — no request is sent. `invalid_date`: filed_after or filed_before is not a valid ISO 8601 calendar date. Other values are possible when a failure originates below the handler." - removed
Output schema / properties / next_cursor / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / next_cursor / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / results / items / properties / assigned_to / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / results / items / properties / assigned_to / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / results / items / properties / date_terminated / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / results / items / properties / date_terminated / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / results / items / properties / pacer_case_id / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / results / items / properties / pacer_case_id / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / results / items / properties / referred_to / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / results / items / properties / referred_to / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / results / items / properties / sample_documents / items / properties / document_number / anyOfRemoved value: -[ - { - "type": "number" - }, - { - "type": "null" - } -] - added
Output schema / properties / results / items / properties / sample_documents / items / properties / document_number / typeAdded value: +[ + "number", + "null" +] - removed
Output schema / properties / results / items / properties / sample_documents / items / properties / entry_number / anyOfRemoved value: -[ - { - "type": "number" - }, - { - "type": "null" - } -] - added
Output schema / properties / results / items / properties / sample_documents / items / properties / entry_number / typeAdded value: +[ + "number", + "null" +] - removed
Output schema / properties / results / items / properties / sample_documents / items / properties / filepath_local / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / results / items / properties / sample_documents / items / properties / filepath_local / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / results / items / properties / sample_documents / items / properties / page_count / anyOfRemoved value: -[ - { - "type": "number" - }, - { - "type": "null" - } -] - added
Output schema / properties / results / items / properties / sample_documents / items / properties / page_count / typeAdded value: +[ + "number", + "null" +]
- Changed
courtlistener_search_financial_disclosures9 fields changed- changed
Output schema / properties / error / properties / data / properties / reason / descriptionPrevious value: -"Machine-readable failure mode. Declared by this tool: `rate_limited`: 429 response from CourtListener. Other values are possible when a failure originates below the handler."New value: +"Machine-readable failure mode. Declared by this tool: `rate_limited`: 429 from CourtListener, or no request slot opened within the wait budget. Other values are possible when a failure originates below the handler." - removed
Output schema / properties / next_cursor / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / next_cursor / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / results / items / properties / page_count / anyOfRemoved value: -[ - { - "type": "number" - }, - { - "type": "null" - } -] - added
Output schema / properties / results / items / properties / page_count / typeAdded value: +[ + "number", + "null" +] - removed
Output schema / properties / results / items / properties / pdf_url / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / results / items / properties / pdf_url / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / results / items / properties / person_id / anyOfRemoved value: -[ - { - "type": "number" - }, - { - "type": "null" - } -] - added
Output schema / properties / results / items / properties / person_id / typeAdded value: +[ + "number", + "null" +]
- Changed
courtlistener_search_judges10 fields changed- changed
Output schema / properties / error / properties / data / properties / reason / descriptionPrevious value: -"Machine-readable failure mode. Declared by this tool: `rate_limited`: 429 response from CourtListener. `empty_query`: q is empty or whitespace-only after trimming — no request is sent. Other values are possible when a failure originates below the handler."New value: +"Machine-readable failure mode. Declared by this tool: `rate_limited`: 429 from CourtListener, or no request slot opened within the wait budget. `empty_query`: q is empty or whitespace-only after trimming — no request is sent. Other values are possible when a failure originates below the handler." - removed
Output schema / properties / next_cursor / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / next_cursor / typeAdded value: +[ + "string", + "null" +] - changed
Output schema / properties / results / items / properties / current_position / anyOfPrevious value: -[ - { - "additionalProperties": false, - "properties": { - "appointer": { - "anyOf": [ - { - "type": "string" - }, - { - "type": "null" - } - ], - "description": "Name of the appointing president (e.g. \"Obama, Barack Hussein, II\"); null if elected or not recorded." - }, - "court": { - "anyOf": [ - { - "type": "string" - }, - { - "type": "null" - } - ], - "description": "Court full name; null for non-judicial positions." - }, - "court_id": { - "anyOf": [ - { - "type": "string" - }, - { - "type": "null" - } - ], - "description": "Court identifier for use in filter parameters; null for non-judicial positions." - }, - "date_start": { - "anyOf": [ - { - "type": "string" - }, - { - "type": "null" - } - ], - "description": "Date the position started; null if not recorded." - }, - "date_termination": { - "anyOf": [ - { - "type": "string" - }, - { - "type": "null" - } - ], - "description": "Date the position ended; null while the judge still holds it." - }, - "job_title": { - "anyOf": [ - { - "type": "string" - }, - { - "type": "null" - } - ], - "description": "Free-text title for non-judicial roles (e.g. \"Assistant district attorney\"); null for judicial positions." - }, - "organization_name": { - "anyOf": [ - { - "type": "string" - }, - { - "type": "null" - } - ], - "description": "Employer for non-judicial roles; null for judicial positions." - }, - "position_type": { - "anyOf": [ - { - "type": "string" - }, - { - "type": "null" - } - ], - "description": "Judicial position title (e.g. \"Judge\", \"Chief Judge\"); null for non-judicial positions — see job_title." - }, - "selection_method": { - "anyOf": [ - { - "type": "string" - }, - { - "type": "null" - } - ], - "description": "How the judge reached the position (e.g. \"Appointment (President)\", \"Election (Partisan)\"); null if not recorded." - }, - "termination_reason": { - "anyOf": [ - { - "type": "string" - }, - { - "type": "null" - } - ], - "description": "Why the position ended (e.g. \"Appointed to Other Judgeship\", \"Retirement\"); null while still serving." - } - }, - "required": [ - "court", - "court_id", - "position_type", - "job_title", - "organization_name", - "appointer", - "selection_method", - "date_start", - "date_termination", - "termination_reason" - ], - "type": "object" - }, - { - "type": "null" - } -]New value: +[ + { + "additionalProperties": false, + "properties": { + "appointer": { + "description": "Name of the appointing president (e.g. \"Obama, Barack Hussein, II\"); null if elected or not recorded.", + "type": [ + "string", + "null" + ] + }, + "court": { + "description": "Court full name; null for non-judicial positions.", + "type": [ + "string", + "null" + ] + }, + "court_id": { + "description": "Court identifier for use in filter parameters; null for non-judicial positions.", + "type": [ + "string", + "null" + ] + }, + "date_start": { + "description": "Date the position started; null if not recorded.", + "type": [ + "string", + "null" + ] + }, + "date_termination": { + "description": "Date the position ended; null while the judge still holds it.", + "type": [ + "string", + "null" + ] + }, + "job_title": { + "description": "Free-text title for non-judicial roles (e.g. \"Assistant district attorney\"); null for judicial positions.", + "type": [ + "string", + "null" + ] + }, + "organization_name": { + "description": "Employer for non-judicial roles; null for judicial positions.", + "type": [ + "string", + "null" + ] + }, + "position_type": { + "description": "Judicial position title (e.g. \"Judge\", \"Chief Judge\"); null for non-judicial positions — see job_title.", + "type": [ + "string", + "null" + ] + }, + "selection_method": { + "description": "How the judge reached the position (e.g. \"Appointment (President)\", \"Election (Partisan)\"); null if not recorded.", + "type": [ + "string", + "null" + ] + }, + "termination_reason": { + "description": "Why the position ended (e.g. \"Appointed to Other Judgeship\", \"Retirement\"); null while still serving.", + "type": [ + "string", + "null" + ] + } + }, + "required": [ + "court", + "court_id", + "position_type", + "job_title", + "organization_name", + "appointer", + "selection_method", + "date_start", + "date_termination", + "termination_reason" + ], + "type": "object" + }, + { + "type": "null" + } +] - removed
Output schema / properties / results / items / properties / dob / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / results / items / properties / dob / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / results / items / properties / dob_city / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / results / items / properties / dob_city / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / results / items / properties / dob_state / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / results / items / properties / dob_state / typeAdded value: +[ + "string", + "null" +]
- Changed
courtlistener_search_opinions10 fields changed- changed
Output schema / properties / error / properties / data / properties / reason / descriptionPrevious value: -"Machine-readable failure mode. Declared by this tool: `rate_limited`: 429 response from CourtListener — minute, hour, or day throttle hit. `invalid_query`: Query uses invalid field syntax or unsupported operators. `empty_query`: q is empty or whitespace-only after trimming — no request is sent. `invalid_date`: filed_after or filed_before is not a valid ISO 8601 calendar date. Other values are possible when a failure originates below the handler."New value: +"Machine-readable failure mode. Declared by this tool: `rate_limited`: 429 from CourtListener, or no request slot opened within the wait budget. `empty_query`: q is empty or whitespace-only after trimming — no request is sent. `invalid_date`: filed_after or filed_before is not a valid ISO 8601 calendar date. Other values are possible when a failure originates below the handler." - changed
Output schema / properties / error / properties / data / properties / reason / examplesPrevious value: -[ - "rate_limited", - "invalid_query", - "empty_query", - "invalid_date" -]New value: +[ + "rate_limited", + "empty_query", + "invalid_date" +] - removed
Output schema / properties / next_cursor / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / next_cursor / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / results / items / properties / opinions / items / properties / author_id / anyOfRemoved value: -[ - { - "type": "number" - }, - { - "type": "null" - } -] - added
Output schema / properties / results / items / properties / opinions / items / properties / author_id / typeAdded value: +[ + "number", + "null" +] - removed
Output schema / properties / results / items / properties / opinions / items / properties / download_url / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / results / items / properties / opinions / items / properties / download_url / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / results / items / properties / opinions / items / properties / local_path / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / results / items / properties / opinions / items / properties / local_path / typeAdded value: +[ + "string", + "null" +]
- Changed
courtlistener_search_oral_arguments9 fields changed- changed
Output schema / properties / error / properties / data / properties / reason / descriptionPrevious value: -"Machine-readable failure mode. Declared by this tool: `rate_limited`: 429 response from CourtListener. `empty_query`: q is empty or whitespace-only after trimming — no request is sent. `invalid_date`: argued_after or argued_before is not a valid ISO 8601 calendar date. Other values are possible when a failure originates below the handler."New value: +"Machine-readable failure mode. Declared by this tool: `rate_limited`: 429 from CourtListener, or no request slot opened within the wait budget. `empty_query`: q is empty or whitespace-only after trimming — no request is sent. `invalid_date`: argued_after or argued_before is not a valid ISO 8601 calendar date. Other values are possible when a failure originates below the handler." - removed
Output schema / properties / next_cursor / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / next_cursor / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / results / items / properties / date_argued / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / results / items / properties / date_argued / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / results / items / properties / download_url / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / results / items / properties / download_url / typeAdded value: +[ + "string", + "null" +] - removed
Output schema / properties / results / items / properties / local_path / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - added
Output schema / properties / results / items / properties / local_path / typeAdded value: +[ + "string", + "null" +]
14 tool updates
- Changed
courtlistener_get_citations6 fields changed- changed
Input schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema" - added
Input schema / additionalPropertiesAdded value: +false - changed
Output schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema" - added
Output schema / anyOfAdded value: +[ + { + "not": { + "required": [ + "error" + ] + }, + "required": [ + "source_cluster_id", + "source_case_name", + "direction", + "results", + "next_cursor", + "totalCount" + ] + }, + { + "required": [ + "error" + ] + } +] - added
Output schema / properties / errorAdded value: +{ + "additionalProperties": {}, + "description": "Present when the call failed. Absent on success.", + "properties": { + "code": { + "description": "JSON-RPC error code for this failure.", + "maximum": 9007199254740991, + "minimum": -9007199254740991, + "type": "integer" + }, + "data": { + "additionalProperties": {}, + "properties": { + "reason": { + "description": "Machine-readable failure mode. Declared by this tool: `not_found`: Cluster ID does not exist in CourtListener. Both directions resolve the source cluster before searching, so a bad ID fails here rather than returning an empty network. `rate_limited`: 429 response from CourtListener. `invalid_date`: filed_after is not a valid ISO 8601 calendar date. Other values are possible when a failure originates below the handler.", + "examples": [ + "not_found", + "rate_limited", + "invalid_date" + ], + "type": "string" + }, + "recovery": { + "additionalProperties": {}, + "description": "Actionable next step for the caller.", + "properties": { + "hint": { + "type": "string" + } + }, + "required": [ + "hint" + ], + "type": "object" + }, + "retryable": { + "description": "Whether retrying may succeed.", + "type": "boolean" + } + }, + "type": "object" + }, + "message": { + "description": "Human-readable description of what went wrong.", + "type": "string" + } + }, + "required": [ + "code", + "message" + ], + "type": "object" +} - removed
Output schema / requiredRemoved value: -[ - "source_cluster_id", - "source_case_name", - "direction", - "results", - "next_cursor", - "totalCount" -]
- Changed
courtlistener_get_docket6 fields changed- changed
Input schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema" - added
Input schema / additionalPropertiesAdded value: +false - changed
Output schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema" - added
Output schema / anyOfAdded value: +[ + { + "not": { + "required": [ + "error" + ] + }, + "required": [ + "docket_id", + "case_name", + "case_name_full", + "court", + "court_id", + "date_filed", + "date_terminated", + "docket_number", + "pacer_case_id", + "assigned_to", + "referred_to", + "cause", + "jury_demand", + "jurisdiction_type", + "total_entries", + "entries_page", + "next_cursor", + "entries" + ] + }, + { + "required": [ + "error" + ] + } +] - added
Output schema / properties / errorAdded value: +{ + "additionalProperties": {}, + "description": "Present when the call failed. Absent on success.", + "properties": { + "code": { + "description": "JSON-RPC error code for this failure.", + "maximum": 9007199254740991, + "minimum": -9007199254740991, + "type": "integer" + }, + "data": { + "additionalProperties": {}, + "properties": { + "reason": { + "description": "Machine-readable failure mode. Declared by this tool: `not_found`: Docket ID does not exist in CourtListener. `rate_limited`: 429 response from CourtListener. Other values are possible when a failure originates below the handler.", + "examples": [ + "not_found", + "rate_limited" + ], + "type": "string" + }, + "recovery": { + "additionalProperties": {}, + "description": "Actionable next step for the caller.", + "properties": { + "hint": { + "type": "string" + } + }, + "required": [ + "hint" + ], + "type": "object" + }, + "retryable": { + "description": "Whether retrying may succeed.", + "type": "boolean" + } + }, + "type": "object" + }, + "message": { + "description": "Human-readable description of what went wrong.", + "type": "string" + } + }, + "required": [ + "code", + "message" + ], + "type": "object" +} - removed
Output schema / requiredRemoved value: -[ - "docket_id", - "case_name", - "case_name_full", - "court", - "court_id", - "date_filed", - "date_terminated", - "docket_number", - "pacer_case_id", - "assigned_to", - "referred_to", - "cause", - "jury_demand", - "jurisdiction_type", - "total_entries", - "entries_page", - "next_cursor", - "entries" -]
- Changed
courtlistener_get_financial_disclosure6 fields changed- changed
Input schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema" - added
Input schema / additionalPropertiesAdded value: +false - changed
Output schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema" - added
Output schema / anyOfAdded value: +[ + { + "not": { + "required": [ + "error" + ] + }, + "required": [ + "disclosure_id", + "person_id", + "year", + "report_type", + "page_count", + "has_been_extracted", + "is_amended", + "pdf_url", + "counts", + "kind" + ] + }, + { + "required": [ + "error" + ] + } +] - added
Output schema / properties / errorAdded value: +{ + "additionalProperties": {}, + "description": "Present when the call failed. Absent on success.", + "properties": { + "code": { + "description": "JSON-RPC error code for this failure.", + "maximum": 9007199254740991, + "minimum": -9007199254740991, + "type": "integer" + }, + "data": { + "additionalProperties": {}, + "properties": { + "reason": { + "description": "Machine-readable failure mode. Declared by this tool: `not_found`: Disclosure ID does not exist in CourtListener. `rate_limited`: 429 response from CourtListener. Other values are possible when a failure originates below the handler.", + "examples": [ + "not_found", + "rate_limited" + ], + "type": "string" + }, + "recovery": { + "additionalProperties": {}, + "description": "Actionable next step for the caller.", + "properties": { + "hint": { + "type": "string" + } + }, + "required": [ + "hint" + ], + "type": "object" + }, + "retryable": { + "description": "Whether retrying may succeed.", + "type": "boolean" + } + }, + "type": "object" + }, + "message": { + "description": "Human-readable description of what went wrong.", + "type": "string" + } + }, + "required": [ + "code", + "message" + ], + "type": "object" +} - removed
Output schema / requiredRemoved value: -[ - "disclosure_id", - "person_id", - "year", - "report_type", - "page_count", - "has_been_extracted", - "is_amended", - "pdf_url", - "counts", - "kind" -]
- Changed
courtlistener_get_judge6 fields changed- changed
Input schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema" - added
Input schema / additionalPropertiesAdded value: +false - changed
Output schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema" - added
Output schema / anyOfAdded value: +[ + { + "not": { + "required": [ + "error" + ] + }, + "required": [ + "person_id", + "name", + "gender", + "dob", + "dob_granularity", + "dob_city", + "dob_state", + "dod", + "dod_granularity", + "fjc_id", + "aba_ratings", + "political_affiliations", + "education", + "positions", + "positionsShown", + "truncated" + ] + }, + { + "required": [ + "error" + ] + } +] - added
Output schema / properties / errorAdded value: +{ + "additionalProperties": {}, + "description": "Present when the call failed. Absent on success.", + "properties": { + "code": { + "description": "JSON-RPC error code for this failure.", + "maximum": 9007199254740991, + "minimum": -9007199254740991, + "type": "integer" + }, + "data": { + "additionalProperties": {}, + "properties": { + "reason": { + "description": "Machine-readable failure mode. Declared by this tool: `not_found`: Person ID does not exist in CourtListener. `rate_limited`: 429 response from CourtListener. Other values are possible when a failure originates below the handler.", + "examples": [ + "not_found", + "rate_limited" + ], + "type": "string" + }, + "recovery": { + "additionalProperties": {}, + "description": "Actionable next step for the caller.", + "properties": { + "hint": { + "type": "string" + } + }, + "required": [ + "hint" + ], + "type": "object" + }, + "retryable": { + "description": "Whether retrying may succeed.", + "type": "boolean" + } + }, + "type": "object" + }, + "message": { + "description": "Human-readable description of what went wrong.", + "type": "string" + } + }, + "required": [ + "code", + "message" + ], + "type": "object" +} - removed
Output schema / requiredRemoved value: -[ - "person_id", - "name", - "gender", - "dob", - "dob_granularity", - "dob_city", - "dob_state", - "dod", - "dod_granularity", - "fjc_id", - "aba_ratings", - "political_affiliations", - "education", - "positions", - "positionsShown", - "truncated" -]
- Changed
courtlistener_get_opinion6 fields changed- changed
Input schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema" - added
Input schema / additionalPropertiesAdded value: +false - changed
Output schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema" - added
Output schema / anyOfAdded value: +[ + { + "not": { + "required": [ + "error" + ] + }, + "required": [ + "cluster_id", + "case_name", + "case_name_full", + "court", + "court_id", + "date_filed", + "docket_id", + "docket_number", + "judges", + "citations", + "cite_count", + "precedential_status", + "syllabus", + "posture", + "kind" + ] + }, + { + "required": [ + "error" + ] + } +] - added
Output schema / properties / errorAdded value: +{ + "additionalProperties": {}, + "description": "Present when the call failed. Absent on success.", + "properties": { + "code": { + "description": "JSON-RPC error code for this failure.", + "maximum": 9007199254740991, + "minimum": -9007199254740991, + "type": "integer" + }, + "data": { + "additionalProperties": {}, + "properties": { + "reason": { + "description": "Machine-readable failure mode. Declared by this tool: `not_found`: Cluster ID does not exist in CourtListener. `rate_limited`: 429 response from CourtListener. `unknown_section`: A requested sections name matches no opinion variant in this cluster. Other values are possible when a failure originates below the handler.", + "examples": [ + "not_found", + "rate_limited", + "unknown_section" + ], + "type": "string" + }, + "recovery": { + "additionalProperties": {}, + "description": "Actionable next step for the caller.", + "properties": { + "hint": { + "type": "string" + } + }, + "required": [ + "hint" + ], + "type": "object" + }, + "retryable": { + "description": "Whether retrying may succeed.", + "type": "boolean" + } + }, + "type": "object" + }, + "message": { + "description": "Human-readable description of what went wrong.", + "type": "string" + } + }, + "required": [ + "code", + "message" + ], + "type": "object" +} - removed
Output schema / requiredRemoved value: -[ - "cluster_id", - "case_name", - "case_name_full", - "court", - "court_id", - "date_filed", - "docket_id", - "docket_number", - "judges", - "citations", - "cite_count", - "precedential_status", - "syllabus", - "posture", - "kind" -]
- Changed
courtlistener_get_oral_argument6 fields changed- changed
Input schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema" - added
Input schema / additionalPropertiesAdded value: +false - changed
Output schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema" - added
Output schema / anyOfAdded value: +[ + { + "not": { + "required": [ + "error" + ] + }, + "required": [ + "kind" + ] + }, + { + "required": [ + "error" + ] + } +] - added
Output schema / properties / errorAdded value: +{ + "additionalProperties": {}, + "description": "Present when the call failed. Absent on success.", + "properties": { + "code": { + "description": "JSON-RPC error code for this failure.", + "maximum": 9007199254740991, + "minimum": -9007199254740991, + "type": "integer" + }, + "data": { + "additionalProperties": {}, + "properties": { + "reason": { + "description": "Machine-readable failure mode. Declared by this tool: `not_found`: Audio ID does not exist in CourtListener. `rate_limited`: 429 response from CourtListener. `unknown_section`: A requested sections name is not a field of the oral argument record. Other values are possible when a failure originates below the handler.", + "examples": [ + "not_found", + "rate_limited", + "unknown_section" + ], + "type": "string" + }, + "recovery": { + "additionalProperties": {}, + "description": "Actionable next step for the caller.", + "properties": { + "hint": { + "type": "string" + } + }, + "required": [ + "hint" + ], + "type": "object" + }, + "retryable": { + "description": "Whether retrying may succeed.", + "type": "boolean" + } + }, + "type": "object" + }, + "message": { + "description": "Human-readable description of what went wrong.", + "type": "string" + } + }, + "required": [ + "code", + "message" + ], + "type": "object" +} - removed
Output schema / requiredRemoved value: -[ - "kind" -]
- Changed
courtlistener_get_parties6 fields changed- changed
Input schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema" - added
Input schema / additionalPropertiesAdded value: +false - changed
Output schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema" - added
Output schema / anyOfAdded value: +[ + { + "not": { + "required": [ + "error" + ] + }, + "required": [ + "docket_id", + "total_parties", + "next_cursor", + "parties" + ] + }, + { + "required": [ + "error" + ] + } +] - added
Output schema / properties / errorAdded value: +{ + "additionalProperties": {}, + "description": "Present when the call failed. Absent on success.", + "properties": { + "code": { + "description": "JSON-RPC error code for this failure.", + "maximum": 9007199254740991, + "minimum": -9007199254740991, + "type": "integer" + }, + "data": { + "additionalProperties": {}, + "properties": { + "reason": { + "description": "Machine-readable failure mode. Declared by this tool: `not_found`: Docket ID does not exist in CourtListener or has no RECAP party data. `rate_limited`: 429 response from CourtListener. Each call to this tool makes at least two upstream requests. Other values are possible when a failure originates below the handler.", + "examples": [ + "not_found", + "rate_limited" + ], + "type": "string" + }, + "recovery": { + "additionalProperties": {}, + "description": "Actionable next step for the caller.", + "properties": { + "hint": { + "type": "string" + } + }, + "required": [ + "hint" + ], + "type": "object" + }, + "retryable": { + "description": "Whether retrying may succeed.", + "type": "boolean" + } + }, + "type": "object" + }, + "message": { + "description": "Human-readable description of what went wrong.", + "type": "string" + } + }, + "required": [ + "code", + "message" + ], + "type": "object" +} - removed
Output schema / requiredRemoved value: -[ - "docket_id", - "total_parties", - "next_cursor", - "parties" -]
- Changed
courtlistener_lookup_citation6 fields changed- changed
Input schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema" - added
Input schema / additionalPropertiesAdded value: +false - changed
Output schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema" - added
Output schema / anyOfAdded value: +[ + { + "not": { + "required": [ + "error" + ] + }, + "required": [ + "matches", + "queriedCitation" + ] + }, + { + "required": [ + "error" + ] + } +] - added
Output schema / properties / errorAdded value: +{ + "additionalProperties": {}, + "description": "Present when the call failed. Absent on success.", + "properties": { + "code": { + "description": "JSON-RPC error code for this failure.", + "maximum": 9007199254740991, + "minimum": -9007199254740991, + "type": "integer" + }, + "data": { + "additionalProperties": {}, + "properties": { + "reason": { + "description": "Machine-readable failure mode. Declared by this tool: `not_found`: CourtListener could not parse any citation out of the submitted text. A citation that parses but matches nothing is a result with status 404, not this error. `rate_limited`: 429 response from CourtListener. `empty_citation`: citation is empty or whitespace-only after trimming — no request is sent. `citation_too_long`: citation exceeds the 64000-character ceiling CourtListener accepts — no request is sent. Other values are possible when a failure originates below the handler.", + "examples": [ + "not_found", + "rate_limited", + "empty_citation", + "citation_too_long" + ], + "type": "string" + }, + "recovery": { + "additionalProperties": {}, + "description": "Actionable next step for the caller.", + "properties": { + "hint": { + "type": "string" + } + }, + "required": [ + "hint" + ], + "type": "object" + }, + "retryable": { + "description": "Whether retrying may succeed.", + "type": "boolean" + } + }, + "type": "object" + }, + "message": { + "description": "Human-readable description of what went wrong.", + "type": "string" + } + }, + "required": [ + "code", + "message" + ], + "type": "object" +} - removed
Output schema / requiredRemoved value: -[ - "matches", - "queriedCitation" -]
- Changed
courtlistener_lookup_courts6 fields changed- changed
Input schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema" - added
Input schema / additionalPropertiesAdded value: +false - changed
Output schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema" - added
Output schema / anyOfAdded value: +[ + { + "not": { + "required": [ + "error" + ] + }, + "required": [ + "page", + "next_cursor", + "courts", + "all_matching_court_ids", + "all_matching_court_ids_complete", + "totalCount" + ] + }, + { + "required": [ + "error" + ] + } +] - added
Output schema / properties / errorAdded value: +{ + "additionalProperties": {}, + "description": "Present when the call failed. Absent on success.", + "properties": { + "code": { + "description": "JSON-RPC error code for this failure.", + "maximum": 9007199254740991, + "minimum": -9007199254740991, + "type": "integer" + }, + "data": { + "additionalProperties": {}, + "properties": { + "reason": { + "description": "Machine-readable failure mode. Declared by this tool: `rate_limited`: 429 response from CourtListener. Other values are possible when a failure originates below the handler.", + "examples": [ + "rate_limited" + ], + "type": "string" + }, + "recovery": { + "additionalProperties": {}, + "description": "Actionable next step for the caller.", + "properties": { + "hint": { + "type": "string" + } + }, + "required": [ + "hint" + ], + "type": "object" + }, + "retryable": { + "description": "Whether retrying may succeed.", + "type": "boolean" + } + }, + "type": "object" + }, + "message": { + "description": "Human-readable description of what went wrong.", + "type": "string" + } + }, + "required": [ + "code", + "message" + ], + "type": "object" +} - removed
Output schema / requiredRemoved value: -[ - "page", - "next_cursor", - "courts", - "all_matching_court_ids", - "all_matching_court_ids_complete", - "totalCount" -]
- Changed
courtlistener_search_dockets6 fields changed- changed
Input schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema" - added
Input schema / additionalPropertiesAdded value: +false - changed
Output schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema" - added
Output schema / anyOfAdded value: +[ + { + "not": { + "required": [ + "error" + ] + }, + "required": [ + "results", + "next_cursor", + "coverage_note", + "totalCount" + ] + }, + { + "required": [ + "error" + ] + } +] - added
Output schema / properties / errorAdded value: +{ + "additionalProperties": {}, + "description": "Present when the call failed. Absent on success.", + "properties": { + "code": { + "description": "JSON-RPC error code for this failure.", + "maximum": 9007199254740991, + "minimum": -9007199254740991, + "type": "integer" + }, + "data": { + "additionalProperties": {}, + "properties": { + "reason": { + "description": "Machine-readable failure mode. Declared by this tool: `rate_limited`: 429 response from CourtListener. `empty_query`: q is empty or whitespace-only after trimming — no request is sent. `invalid_date`: filed_after or filed_before is not a valid ISO 8601 calendar date. Other values are possible when a failure originates below the handler.", + "examples": [ + "rate_limited", + "empty_query", + "invalid_date" + ], + "type": "string" + }, + "recovery": { + "additionalProperties": {}, + "description": "Actionable next step for the caller.", + "properties": { + "hint": { + "type": "string" + } + }, + "required": [ + "hint" + ], + "type": "object" + }, + "retryable": { + "description": "Whether retrying may succeed.", + "type": "boolean" + } + }, + "type": "object" + }, + "message": { + "description": "Human-readable description of what went wrong.", + "type": "string" + } + }, + "required": [ + "code", + "message" + ], + "type": "object" +} - removed
Output schema / requiredRemoved value: -[ - "results", - "next_cursor", - "coverage_note", - "totalCount" -]
- Changed
courtlistener_search_financial_disclosures6 fields changed- changed
Input schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema" - added
Input schema / additionalPropertiesAdded value: +false - changed
Output schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema" - added
Output schema / anyOfAdded value: +[ + { + "not": { + "required": [ + "error" + ] + }, + "required": [ + "results", + "next_cursor" + ] + }, + { + "required": [ + "error" + ] + } +] - added
Output schema / properties / errorAdded value: +{ + "additionalProperties": {}, + "description": "Present when the call failed. Absent on success.", + "properties": { + "code": { + "description": "JSON-RPC error code for this failure.", + "maximum": 9007199254740991, + "minimum": -9007199254740991, + "type": "integer" + }, + "data": { + "additionalProperties": {}, + "properties": { + "reason": { + "description": "Machine-readable failure mode. Declared by this tool: `rate_limited`: 429 response from CourtListener. Other values are possible when a failure originates below the handler.", + "examples": [ + "rate_limited" + ], + "type": "string" + }, + "recovery": { + "additionalProperties": {}, + "description": "Actionable next step for the caller.", + "properties": { + "hint": { + "type": "string" + } + }, + "required": [ + "hint" + ], + "type": "object" + }, + "retryable": { + "description": "Whether retrying may succeed.", + "type": "boolean" + } + }, + "type": "object" + }, + "message": { + "description": "Human-readable description of what went wrong.", + "type": "string" + } + }, + "required": [ + "code", + "message" + ], + "type": "object" +} - removed
Output schema / requiredRemoved value: -[ - "results", - "next_cursor" -]
- Changed
courtlistener_search_judges6 fields changed- changed
Input schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema" - added
Input schema / additionalPropertiesAdded value: +false - changed
Output schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema" - added
Output schema / anyOfAdded value: +[ + { + "not": { + "required": [ + "error" + ] + }, + "required": [ + "results", + "next_cursor", + "totalCount" + ] + }, + { + "required": [ + "error" + ] + } +] - added
Output schema / properties / errorAdded value: +{ + "additionalProperties": {}, + "description": "Present when the call failed. Absent on success.", + "properties": { + "code": { + "description": "JSON-RPC error code for this failure.", + "maximum": 9007199254740991, + "minimum": -9007199254740991, + "type": "integer" + }, + "data": { + "additionalProperties": {}, + "properties": { + "reason": { + "description": "Machine-readable failure mode. Declared by this tool: `rate_limited`: 429 response from CourtListener. `empty_query`: q is empty or whitespace-only after trimming — no request is sent. Other values are possible when a failure originates below the handler.", + "examples": [ + "rate_limited", + "empty_query" + ], + "type": "string" + }, + "recovery": { + "additionalProperties": {}, + "description": "Actionable next step for the caller.", + "properties": { + "hint": { + "type": "string" + } + }, + "required": [ + "hint" + ], + "type": "object" + }, + "retryable": { + "description": "Whether retrying may succeed.", + "type": "boolean" + } + }, + "type": "object" + }, + "message": { + "description": "Human-readable description of what went wrong.", + "type": "string" + } + }, + "required": [ + "code", + "message" + ], + "type": "object" +} - removed
Output schema / requiredRemoved value: -[ - "results", - "next_cursor", - "totalCount" -]
- Changed
courtlistener_search_opinions6 fields changed- changed
Input schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema" - added
Input schema / additionalPropertiesAdded value: +false - changed
Output schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema" - added
Output schema / anyOfAdded value: +[ + { + "not": { + "required": [ + "error" + ] + }, + "required": [ + "results", + "next_cursor", + "totalCount", + "effectiveQuery" + ] + }, + { + "required": [ + "error" + ] + } +] - added
Output schema / properties / errorAdded value: +{ + "additionalProperties": {}, + "description": "Present when the call failed. Absent on success.", + "properties": { + "code": { + "description": "JSON-RPC error code for this failure.", + "maximum": 9007199254740991, + "minimum": -9007199254740991, + "type": "integer" + }, + "data": { + "additionalProperties": {}, + "properties": { + "reason": { + "description": "Machine-readable failure mode. Declared by this tool: `rate_limited`: 429 response from CourtListener — minute, hour, or day throttle hit. `invalid_query`: Query uses invalid field syntax or unsupported operators. `empty_query`: q is empty or whitespace-only after trimming — no request is sent. `invalid_date`: filed_after or filed_before is not a valid ISO 8601 calendar date. Other values are possible when a failure originates below the handler.", + "examples": [ + "rate_limited", + "invalid_query", + "empty_query", + "invalid_date" + ], + "type": "string" + }, + "recovery": { + "additionalProperties": {}, + "description": "Actionable next step for the caller.", + "properties": { + "hint": { + "type": "string" + } + }, + "required": [ + "hint" + ], + "type": "object" + }, + "retryable": { + "description": "Whether retrying may succeed.", + "type": "boolean" + } + }, + "type": "object" + }, + "message": { + "description": "Human-readable description of what went wrong.", + "type": "string" + } + }, + "required": [ + "code", + "message" + ], + "type": "object" +} - removed
Output schema / requiredRemoved value: -[ - "results", - "next_cursor", - "totalCount", - "effectiveQuery" -]
- Changed
courtlistener_search_oral_arguments6 fields changed- changed
Input schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema" - added
Input schema / additionalPropertiesAdded value: +false - changed
Output schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema" - added
Output schema / anyOfAdded value: +[ + { + "not": { + "required": [ + "error" + ] + }, + "required": [ + "results", + "next_cursor", + "totalCount" + ] + }, + { + "required": [ + "error" + ] + } +] - added
Output schema / properties / errorAdded value: +{ + "additionalProperties": {}, + "description": "Present when the call failed. Absent on success.", + "properties": { + "code": { + "description": "JSON-RPC error code for this failure.", + "maximum": 9007199254740991, + "minimum": -9007199254740991, + "type": "integer" + }, + "data": { + "additionalProperties": {}, + "properties": { + "reason": { + "description": "Machine-readable failure mode. Declared by this tool: `rate_limited`: 429 response from CourtListener. `empty_query`: q is empty or whitespace-only after trimming — no request is sent. `invalid_date`: argued_after or argued_before is not a valid ISO 8601 calendar date. Other values are possible when a failure originates below the handler.", + "examples": [ + "rate_limited", + "empty_query", + "invalid_date" + ], + "type": "string" + }, + "recovery": { + "additionalProperties": {}, + "description": "Actionable next step for the caller.", + "properties": { + "hint": { + "type": "string" + } + }, + "required": [ + "hint" + ], + "type": "object" + }, + "retryable": { + "description": "Whether retrying may succeed.", + "type": "boolean" + } + }, + "type": "object" + }, + "message": { + "description": "Human-readable description of what went wrong.", + "type": "string" + } + }, + "required": [ + "code", + "message" + ], + "type": "object" +} - removed
Output schema / requiredRemoved value: -[ - "results", - "next_cursor", - "totalCount" -]
1 tool update
- Changed
courtlistener_lookup_courts2 fields changed- changed
Input schema / properties / jurisdiction / descriptionPrevious value: -"Jurisdiction type. F=Federal Appellate (circuit courts, SCOTUS), FD=Federal District, FB=Federal Bankruptcy, FBP=Federal Bankruptcy Panel, FS=Federal Special (USITC, FISC, etc.), C=Circuit (historical), I=International, T=Territory, ST=State Trial, SS=State Supreme, SAG=State Attorney General, SAL=State Legislature, SA=State Appellate, S=State (other), TT=Tribal/Territory. Omit to list all."New value: +"Jurisdiction type — CourtListener's own court classification, one code per court: F=Federal Appellate, FD=Federal District, FB=Federal Bankruptcy, FBP=Federal Bankruptcy Panel, FS=Federal Special, S=State Supreme, SA=State Appellate, ST=State Trial, SS=State Special, SAG=State Attorney General, TRS=Tribal Supreme, TRA=Tribal Appellate, TRT=Tribal Trial, TRX=Tribal Special, TS=Territory Supreme, TA=Territory Appellate, TT=Territory Trial, TSP=Territory Special, MA=Military Appellate, MT=Military Trial, C=Committee, I=International. Omit to list all. SCOTUS and the numbered circuits are F; USITC and FISC are FS. Upstream's Testing code is not offered here: /courts/ excludes testing courts from every response, so a filter on it can only ever return nothing. Accepted but matching no court as of the 2026-07-30 snapshot: TSP, MT. Courts whose stored jurisdiction is not one of these codes (njcirctsussex, ohctapp1) are unreachable through this filter at any value — the value they store is not one the filter accepts. Pass those ids straight to the tool that needs them, or list with no jurisdiction filter." - changed
Input schema / properties / jurisdiction / enumPrevious value: -[ - "F", - "FD", - "FB", - "FBP", - "FS", - "C", - "I", - "T", - "ST", - "SS", - "SAG", - "SAL", - "SA", - "S", - "TT" -]New value: +[ + "F", + "FD", + "FB", + "FBP", + "FS", + "S", + "SA", + "ST", + "SS", + "SAG", + "TRS", + "TRA", + "TRT", + "TRX", + "TS", + "TA", + "TT", + "TSP", + "MA", + "MT", + "C", + "I" +]
3 tool updates
- Changed
courtlistener_get_judge5 fields changed- added
Output schema / properties / noticeAdded value: +{ + "description": "Present only when positions[] was truncated: what was withheld.", + "type": "string" +} - changed
Output schema / properties / positions / descriptionPrevious value: -"Every position on record, across all courts — judicial appointments plus non-judicial roles (private practice, prosecutor, professor), which carry no court and describe themselves in job_title."New value: +"Positions on record, across all courts — judicial appointments plus non-judicial roles (private practice, prosecutor, professor), which carry no court and describe themselves in job_title. CourtListener paginates this list and the walk is bounded, so read the truncated flag before treating it as a complete career." - added
Output schema / properties / positionsShownAdded value: +{ + "description": "Number of position records returned.", + "type": "number" +} - added
Output schema / properties / truncatedAdded value: +{ + "description": "True when the bounded /positions/ page walk stopped with pages outstanding — positions[] is then a prefix of the person's record, not the whole of it. False when the walk reached the end.", + "type": "boolean" +} - changed
Output schema / requiredPrevious value: -[ - "person_id", - "name", - "gender", - "dob", - "dob_granularity", - "dob_city", - "dob_state", - "dod", - "dod_granularity", - "fjc_id", - "aba_ratings", - "political_affiliations", - "education", - "positions" -]New value: +[ + "person_id", + "name", + "gender", + "dob", + "dob_granularity", + "dob_city", + "dob_state", + "dod", + "dod_granularity", + "fjc_id", + "aba_ratings", + "political_affiliations", + "education", + "positions", + "positionsShown", + "truncated" +]
- Changed
courtlistener_lookup_citation5 fields changed- added
Input schema / properties / max_court_lookupsAdded value: +{ + "default": 4, + "description": "How many distinct dockets this call may spend a request on to resolve cluster courts. The lookup itself is metered separately by CourtListener (per citation submitted), so this budget is drawn entirely from the ordinary per-request allowance — published free tier 5/min, 50/hour, 125/day, varying by token tier. 0 skips court resolution and costs nothing beyond the lookup; 20 is the ceiling. Clusters past the budget come back with court null and court_resolution \"over_budget\".", + "maximum": 20, + "minimum": 0, + "type": "integer" +} - changed
Output schema / properties / matches / items / properties / clusters / items / properties / court / descriptionPrevious value: -"Court display name. The citation-lookup payload carries no court, so this is resolved from the cluster's docket — one extra request each, capped at 4 distinct dockets per call. Null when that lookup was skipped past the cap, failed, or the cluster has no docket_id; the response notice reports how many clusters were left unresolved. Pass docket_id to courtlistener_get_docket, or cluster_id to courtlistener_get_opinion, to resolve one."New value: +"Court display name. The citation-lookup payload carries no court, so this is resolved from the cluster's docket — one extra request each, capped by max_court_lookups (default 4 distinct dockets per call). Null when that lookup was skipped past the budget, failed, or the cluster has no docket_id; court_resolution says which. Pass docket_id to courtlistener_get_docket, or cluster_id to courtlistener_get_opinion, to resolve one." - added
Output schema / properties / matches / items / properties / clusters / items / properties / court_resolutionAdded value: +{ + "description": "Why court/court_id are or are not populated: \"resolved\" the docket lookup returned a court; \"no_docket\" the cluster carries no docket_id, so nothing can be resolved; \"lookup_failed\" a request was spent on the docket and it yielded no court; \"over_budget\" no request was spent because max_court_lookups ran out or the walk stopped on a rate limit — raise max_court_lookups or fetch that docket directly.", + "enum": [ + "resolved", + "no_docket", + "lookup_failed", + "over_budget" + ], + "type": "string" +} - changed
Output schema / properties / matches / items / properties / clusters / items / requiredPrevious value: -[ - "cluster_id", - "case_name", - "court", - "court_id", - "date_filed", - "docket_id", - "citations", - "cite_count", - "precedential_status", - "judges" -]New value: +[ + "cluster_id", + "case_name", + "court", + "court_id", + "court_resolution", + "date_filed", + "docket_id", + "citations", + "cite_count", + "precedential_status", + "judges" +] - changed
Output schema / properties / notice / descriptionPrevious value: -"Caveats on this result: a recovery hint when no citation in the input resolved to a case, and a count of clusters whose court the per-call docket cap left unresolved. Absent when neither applies."New value: +"Caveats on this result: a recovery hint when no citation in the input resolved to a case, and counts of the clusters whose court went unresolved — split by whether the per-call docket budget ran out or an attempted lookup returned nothing, since only the first is worth retrying with a larger budget. Absent when none applies."
- Changed
courtlistener_lookup_courts4 fields changed- added
Output schema / properties / all_matching_court_idsAdded value: +{ + "description": "Every court id matching the same filters, from a snapshot of /courts/ bundled with this server (taken 2026-07-30) — the complete set, not just this page, and free of any request. Paging `courts` is only needed for the fields a court id alone does not carry (full_name, citation_string, scraper flags). Empty when more than 1000 courts match, since a prefix of the set would be indistinguishable from the whole of it — check all_matching_court_ids_complete before reading emptiness as \"no courts match\". A court added or retired upstream since the snapshot date appears in `courts` but may be missing here.", + "items": { + "type": "string" + }, + "type": "array" +} - added
Output schema / properties / all_matching_court_ids_completeAdded value: +{ + "description": "True when all_matching_court_ids holds every matching court id. False when more than 1000 courts match: the list is withheld whole rather than truncated, and the notice gives the count and how to narrow.", + "type": "boolean" +} - changed
Output schema / properties / courts / descriptionPrevious value: -"Matching courts."New value: +"Matching courts on this page." - changed
Output schema / requiredPrevious value: -[ - "page", - "next_cursor", - "courts", - "totalCount" -]New value: +[ + "page", + "next_cursor", + "courts", + "all_matching_court_ids", + "all_matching_court_ids_complete", + "totalCount" +]
4 tool updates
- Changed
courtlistener_get_oral_argument6 fields changed- changed
Input schema / properties / sections / descriptionPrevious value: -"Section identifiers to retrieve in full, from a prior outline response (e.g. [\"transcript\"]). Omit for the full record, or an outline if it overflows the inline budget."New value: +"Section identifiers to retrieve, from a prior outline response — [\"transcript\"] is the only one that adds anything, since every other field is returned regardless. A selection that omits \"transcript\" therefore returns the record without it. Omit this argument entirely for the whole record, or the record minus an oversized transcript." - changed
Output schema / properties / kind / descriptionPrevious value: -"'full' returns the record (or the selected sections); 'outline' lists retrievable sections when the transcript overflows the inline byte budget."New value: +"'full' carries the transcript inline; 'outline' withholds it and lists it as a retrievable section because it overflows the inline byte budget. Every other field of the record is present either way." - changed
Output schema / properties / retrieval_notice / descriptionPrevious value: -"How to re-call the tool for specific sections when the record overflows."New value: +"How to re-call the tool for the transcript when it overflows the inline budget." - changed
Output schema / properties / sections / descriptionPrevious value: -"Retrievable sections, largest first — pass names to `sections` on a re-call."New value: +"Sections withheld from this response — only ever `transcript`; pass its name to `sections` on a re-call. Absent when nothing was withheld." - changed
Output schema / properties / sections / items / descriptionPrevious value: -"A retrievable section of the record and its serialized byte size."New value: +"A withheld section of the record and its serialized byte size." - changed
Output schema / properties / transcript / descriptionPrevious value: -"Speech-to-text transcript; empty string if transcription has not completed."New value: +"Speech-to-text transcript; empty string if transcription has not completed. The only field an outline response withholds — re-call with sections:[\"transcript\"] to retrieve it."
- Changed
courtlistener_get_parties7 fields changed- added
Input schema / properties / cursorAdded value: +{ + "description": "Pagination cursor from a previous response's next_cursor field. Omit for the first page. This is an opaque token, not a page number — CourtListener cursor-paginates this endpoint, so a numeric value selects nothing and re-serves the first page.", + "type": "string" +} - removed
Input schema / properties / pageRemoved value: -{ - "default": 1, - "description": "Page number (1-indexed). Use with page_size to paginate large party lists.", - "maximum": 9007199254740991, - "minimum": 1, - "type": "integer" -} - changed
Output schema / properties / next_cursor / descriptionPrevious value: -"Next page number to pass as the `page` argument (this list is page-paginated); null when this is the last page."New value: +"Opaque pagination cursor for the next page — pass it back as the `cursor` argument; null when this is the last page." - removed
Output schema / properties / pageRemoved value: -{ - "description": "Current page number.", - "type": "number" -} - changed
Output schema / properties / totalCount / descriptionPrevious value: -"Total parties on this docket across all pages — present only when the API reports a numeric count (this endpoint returns it as a URL by default, so it is absent for any list spanning more than one page)."New value: +"Total parties on this docket across all pages — this endpoint reports its count as a URL rather than a number, so the total is only derivable when the first page is also the last, and is absent for any list spanning more than one page." - changed
Output schema / properties / total_parties / descriptionPrevious value: -"Total parties on this docket across all pages; null when upstream reports no count (a multi-page list whose total is unknown until the last page)."New value: +"Total parties on this docket across all pages; null when no total is derivable — CourtListener serves the count as a URL rather than a number here, so it is only known when the first page is also the last." - changed
Output schema / requiredPrevious value: -[ - "docket_id", - "total_parties", - "page", - "next_cursor", - "parties" -]New value: +[ + "docket_id", + "total_parties", + "next_cursor", + "parties" +]
- Changed
courtlistener_lookup_citation10 fields changed- changed
Input schema / properties / citation / descriptionPrevious value: -"Legal citation string to resolve (e.g., \"410 U.S. 113\", \"347 U.S. 483\", \"93 S. Ct. 705\"). Supports standard reporter formats."New value: +"Text to extract citations from — normally a single citation (e.g., \"410 U.S. 113\", \"347 U.S. 483\", \"93 S. Ct. 705\"), but any passage works and every citation in it is resolved. Supports standard reporter formats. Up to 64000 characters, which is CourtListener's own ceiling; a longer passage is rejected here rather than spending a request to be refused upstream." - removed
Output schema / properties / case_nameRemoved value: -{ - "anyOf": [ - { - "type": "string" - }, - { - "type": "null" - } - ], - "description": "Case name; null if not found." -} - removed
Output schema / properties / citationsRemoved value: -{ - "description": "All known citation strings for this case.", - "items": { - "type": "string" - }, - "type": "array" -} - removed
Output schema / properties / cluster_idRemoved value: -{ - "anyOf": [ - { - "type": "number" - }, - { - "type": "null" - } - ], - "description": "Opinion cluster ID — null if the citation is not in the CourtListener database." -} - removed
Output schema / properties / courtRemoved value: -{ - "anyOf": [ - { - "type": "string" - }, - { - "type": "null" - } - ], - "description": "Court display name; null if not found." -} - removed
Output schema / properties / date_filedRemoved value: -{ - "anyOf": [ - { - "type": "string" - }, - { - "type": "null" - } - ], - "description": "Date the opinion was filed; null if not found." -} - added
Output schema / properties / matchesAdded value: +{ + "description": "One entry per citation CourtListener extracted from the input, in the order they appear.", + "items": { + "additionalProperties": false, + "description": "One citation found in the submitted text and everything it resolved to.", + "properties": { + "citation": { + "description": "The citation as CourtListener matched it in the submitted text.", + "type": "string" + }, + "clusters": { + "description": "Cases this citation resolved to — empty when status is not 200 or 300, and more than one when status is 300.", + "items": { + "additionalProperties": false, + "description": "An opinion cluster this citation resolved to.", + "properties": { + "case_name": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ], + "description": "Case name; null if not recorded." + }, + "citations": { + "description": "All known citation strings for this case.", + "items": { + "type": "string" + }, + "type": "array" + }, + "cite_count": { + "anyOf": [ + { + "type": "number" + }, + { + "type": "null" + } + ], + "description": "Times other opinions cite this case — a rough authority weight. Null if not recorded." + }, + "cluster_id": { + "anyOf": [ + { + "type": "number" + }, + { + "type": "null" + } + ], + "description": "Opinion cluster ID — pass to courtlistener_get_opinion. Null when upstream sent no ID." + }, + "court": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ], + "description": "Court display name. The citation-lookup payload carries no court, so this is resolved from the cluster's docket — one extra request each, capped at 4 distinct dockets per call. Null when that lookup was skipped past the cap, failed, or the cluster has no docket_id; the response notice reports how many clusters were left unresolved. Pass docket_id to courtlistener_get_docket, or cluster_id to courtlistener_get_opinion, to resolve one." + }, + "court_id": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ], + "description": "Court identifier for the `court` filter on the search tools (e.g. \"scotus\"); null under the same conditions as `court`." + }, + "date_filed": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ], + "description": "Date the opinion was filed; null if not recorded." + }, + "docket_id": { + "anyOf": [ + { + "type": "number" + }, + { + "type": "null" + } + ], + "description": "Linked docket — pass to courtlistener_get_docket. Null if not recorded." + }, + "judges": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ], + "description": "Free-text judge names; null or empty if not recorded." + }, + "precedential_status": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ], + "description": "Publication status (e.g. \"Published\", \"Unpublished\"); null if not recorded." + } + }, + "required": [ + "cluster_id", + "case_name", + "court", + "court_id", + "date_filed", + "docket_id", + "citations", + "cite_count", + "precedential_status", + "judges" + ], + "type": "object" + }, + "type": "array" + }, + "error_message": { + "description": "CourtListener's explanation when status is not 200; empty string otherwise.", + "type": "string" + }, + "normalized_citation": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ], + "description": "Canonical citation form used by CourtListener; null if not resolved." + }, + "status": { + "description": "Resolution status for this citation alone: 200 one case, 300 several candidates, 400 unrecognized reporter, 404 no case found, 429 past the per-request citation cap. Not the status of the request, which succeeded.", + "type": "number" + }, + "status_label": { + "description": "status decoded to a label.", + "type": "string" + } + }, + "required": [ + "citation", + "normalized_citation", + "status", + "status_label", + "error_message", + "clusters" + ], + "type": "object" + }, + "type": "array" +} - removed
Output schema / properties / normalized_citationRemoved value: -{ - "anyOf": [ - { - "type": "string" - }, - { - "type": "null" - } - ], - "description": "Canonical citation form used by CourtListener; null if not resolved." -} - changed
Output schema / properties / notice / descriptionPrevious value: -"Recovery hint when the citation is not in the database — suggests alternative lookup strategies."New value: +"Caveats on this result: a recovery hint when no citation in the input resolved to a case, and a count of clusters whose court the per-call docket cap left unresolved. Absent when neither applies." - changed
Output schema / requiredPrevious value: -[ - "cluster_id", - "case_name", - "court", - "date_filed", - "citations", - "normalized_citation", - "queriedCitation" -]New value: +[ + "matches", + "queriedCitation" +]
- Changed
courtlistener_lookup_courts4 fields changed- removed
Input schema / properties / in_useRemoved value: -{ - "default": true, - "description": "When true (default), only return courts currently scraped by CourtListener. Set to false to include historical or inactive courts.", - "type": "boolean" -} - changed
Input schema / properties / page / descriptionPrevious value: -"Page number (1-indexed). CourtListener caps /courts/ at ~20 rows per page regardless of size, so the full list (~472 courts) spans ~24 pages — pass the next_cursor from a previous response here to page through them."New value: +"Page number (1-indexed). CourtListener serves /courts/ at a fixed 20 rows per page and ignores any requested page size, so the number of pages is the enrichment totalCount divided by 20 — there is no way to pull a larger page. Pass the next_cursor from a previous response here to walk them one call at a time." - added
Input schema / properties / statusAdded value: +{ + "default": "active", + "description": "Which bench to return. 'active' (default) returns only courts CourtListener currently scrapes; 'inactive' returns only the historical and defunct courts it no longer scrapes; 'any' returns both. The two filtered sets are disjoint, so 'any' is the only value that reaches the whole list — but reaching all of it means paging, one call per 20 courts, and the inactive bench is several times larger than the active one. Prefer the narrowest value that answers the question, and narrow with jurisdiction rather than paging the full list.", + "enum": [ + "active", + "inactive", + "any" + ], + "type": "string" +} - changed
Output schema / properties / next_cursor / descriptionPrevious value: -"Next page number to pass as the `page` argument (this list is page-paginated at ~20 rows/page); null when this is the last page."New value: +"Next page number to pass as the `page` argument (this list is page-paginated at a fixed 20 rows/page); null when this is the last page — a non-null value means the courts shown are a partial view of the filtered set."
2 tool updates
- Changed
courtlistener_get_judge21 fields changed- changed
Output schema / properties / dob / descriptionPrevious value: -"Date of birth; null if not recorded."New value: +"Date of birth as CourtListener stores it, always full ISO 8601 — but the month and day are placeholders unless dob_granularity is \"day\". Read dob_granularity before presenting this as an exact date. Null if not recorded." - added
Output schema / properties / dob_granularityAdded value: +{ + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ], + "description": "Precision actually recorded for dob: \"year\", \"month\", or \"day\". Null when CourtListener recorded no precision. An unrecognized upstream value passes through unchanged." +} - changed
Output schema / properties / dod / descriptionPrevious value: -"Date of death; null if living or not recorded."New value: +"Date of death as CourtListener stores it, always full ISO 8601 — precision qualified by dod_granularity, as with dob. Null if living or not recorded." - added
Output schema / properties / dod_granularityAdded value: +{ + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ], + "description": "Precision actually recorded for dod: \"year\", \"month\", or \"day\". Null when CourtListener recorded no precision." +} - changed
Output schema / properties / education / items / properties / degree / descriptionPrevious value: -"Degree level; null if not recorded."New value: +"Raw CourtListener degree-level code (e.g. \"ba\"); null if not recorded." - added
Output schema / properties / education / items / properties / degree_labelAdded value: +{ + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ], + "description": "Degree level expanded to a readable label (e.g. \"Juris Doctor (J.D.)\"). An unmapped code passes through as the code itself; null if not recorded." +} - changed
Output schema / properties / education / items / requiredPrevious value: -[ - "school", - "degree", - "year" -]New value: +[ + "school", + "degree", + "degree_label", + "year" +] - changed
Output schema / properties / positions / descriptionPrevious value: -"All judicial positions held, across all courts."New value: +"Every position on record, across all courts — judicial appointments plus non-judicial roles (private practice, prosecutor, professor), which carry no court and describe themselves in job_title." - changed
Output schema / properties / positions / items / descriptionPrevious value: -"Judicial position record."New value: +"Position record — judicial or otherwise." - changed
Output schema / properties / positions / items / properties / date_start / descriptionPrevious value: -"Date position started; null if not recorded."New value: +"Date the position started as CourtListener stores it, always full ISO 8601 — the month and day are placeholders unless date_start_granularity is \"day\". Null if not recorded." - added
Output schema / properties / positions / items / properties / date_start_granularityAdded value: +{ + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ], + "description": "Precision actually recorded for date_start: \"year\", \"month\", or \"day\". Null when CourtListener recorded no precision." +} - changed
Output schema / properties / positions / items / properties / date_termination / descriptionPrevious value: -"Date position ended; null if current."New value: +"Date the position ended as CourtListener stores it, always full ISO 8601 — precision qualified by date_termination_granularity. Null if current." - added
Output schema / properties / positions / items / properties / date_termination_granularityAdded value: +{ + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ], + "description": "Precision actually recorded for date_termination: \"year\", \"month\", or \"day\". Null when CourtListener recorded no precision." +} - added
Output schema / properties / positions / items / properties / job_titleAdded value: +{ + "description": "Free-text title for a role with no position_type code (e.g. \"Assistant district attorney\"); empty on judicial rows.", + "type": "string" +} - added
Output schema / properties / positions / items / properties / organization_nameAdded value: +{ + "description": "Employer for a non-judicial role; empty on judicial rows, which use court.", + "type": "string" +} - changed
Output schema / properties / positions / items / properties / position_type / descriptionPrevious value: -"Position title (e.g., \"District Judge\", \"Circuit Judge\", \"Justice\")."New value: +"Raw CourtListener position-type code (e.g. \"jud\", \"c-jud\") — the value the /positions/ position_type filter takes. Empty for non-judicial roles, which describe themselves in job_title." - added
Output schema / properties / positions / items / properties / position_type_labelAdded value: +{ + "description": "Position type expanded to a readable label (e.g. \"Judge\", \"Chief Judge\"). An unmapped code passes through as the code itself; empty for non-judicial roles.", + "type": "string" +} - changed
Output schema / properties / positions / items / properties / termination_reason / descriptionPrevious value: -"Reason for termination; null if still serving."New value: +"Raw CourtListener termination-reason code (e.g. \"other_pos\"); null if still serving." - added
Output schema / properties / positions / items / properties / termination_reason_labelAdded value: +{ + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ], + "description": "Termination reason expanded to a readable label (e.g. \"Appointed to Other Judgeship\"). An unmapped code passes through as the code itself; null if still serving." +} - changed
Output schema / properties / positions / items / requiredPrevious value: -[ - "court", - "court_id", - "position_type", - "appointer", - "nomination_process", - "date_nominated", - "date_confirmation", - "date_start", - "date_termination", - "termination_reason" -]New value: +[ + "court", + "court_id", + "position_type", + "position_type_label", + "job_title", + "organization_name", + "appointer", + "nomination_process", + "date_nominated", + "date_confirmation", + "date_start", + "date_start_granularity", + "date_termination", + "date_termination_granularity", + "termination_reason", + "termination_reason_label" +] - changed
Output schema / requiredPrevious value: -[ - "person_id", - "name", - "gender", - "dob", - "dob_city", - "dob_state", - "dod", - "fjc_id", - "aba_ratings", - "political_affiliations", - "education", - "positions" -]New value: +[ + "person_id", + "name", + "gender", + "dob", + "dob_granularity", + "dob_city", + "dob_state", + "dod", + "dod_granularity", + "fjc_id", + "aba_ratings", + "political_affiliations", + "education", + "positions" +]
- Changed
courtlistener_get_opinion3 fields changed- changed
Output schema / properties / opinions / items / properties / type / descriptionPrevious value: -"Opinion type: \"lead-opinion\", \"concurrence\", \"dissent\", \"combined-opinion\", etc."New value: +"Raw CourtListener opinion-type code (e.g. \"030concurrence\"); the numeric prefix is a sort key, not part of the type. Empty when upstream recorded none." - added
Output schema / properties / opinions / items / properties / type_labelAdded value: +{ + "description": "Opinion type expanded to the label courtlistener_search_opinions serves for the same variant: \"lead-opinion\", \"concurrence-opinion\", \"dissent\", \"combined-opinion\", etc. An unmapped code passes through as the code itself.", + "type": "string" +} - changed
Output schema / properties / opinions / items / requiredPrevious value: -[ - "id", - "type", - "author_id", - "per_curiam", - "html_text", - "plain_text", - "cites", - "download_url" -]New value: +[ + "id", + "type", + "type_label", + "author_id", + "per_curiam", + "html_text", + "plain_text", + "cites", + "download_url" +]
1 tool update
- Changed
courtlistener_get_citations3 fields changed- changed
Input schema / properties / page_size / descriptionPrevious value: -"Number of results to request (default 20). For direction=\"cited_by\", CourtListener enforces a minimum of 20 results per page regardless of the value passed — you will always receive at least 20 results. direction=\"citing\" returns at most page_size (the cited-opinion list is sliced before querying) — fewer when the opinion cites fewer than page_size distinct opinions. Each citation tool call costs one request against the rate limit — keep low for multi-hop traversal."New value: +"Number of results to request (default 20). For direction=\"cited_by\", CourtListener enforces a minimum of 20 results per page regardless of the value passed — you will always receive at least 20 results. direction=\"citing\" returns at most page_size (the cited-opinion list is sliced before querying) — fewer when the opinion cites fewer than page_size distinct opinions. Either direction costs three requests against the rate limit (a case with many opinion variants costs one more per extra variant page) — keep low for multi-hop traversal." - changed
Output schema / properties / notice / descriptionPrevious value: -"Recovery hint when no citations are found — echoes direction and filters, suggests alternatives."New value: +"Context when no citations are returned — either that this page had no match under the filters and more pages remain, or a recovery hint echoing direction and filters." - changed
Output schema / properties / totalCount / descriptionPrevious value: -"Total citations in the requested direction."New value: +"Total citations in the requested direction. For \"cited_by\" it counts matching clusters with the court and filed_after filters applied. For \"citing\" it counts the distinct opinions this case cites, before any filter — so it exceeds what the filters make reachable, and runs higher than the result rows, which are clusters (several cited opinions in one case collapse to one row)."
1 tool update
- Changed
courtlistener_get_parties9 fields changed- changed
Input schema / properties / page_size / descriptionPrevious value: -"Number of parties per page (1–10). Each call makes two upstream requests (parties + attorney batch) — keep low to stay within the free-tier rate limit."New value: +"Requested number of parties per page (1–10). CourtListener paginates this endpoint at a fixed size and does not honor the requested value, so a page can come back larger than asked for." - added
Output schema / properties / parties / items / properties / attorneys / items / properties / date_actionAdded value: +{ + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ], + "description": "Date the attorney–party relationship ended; null while the attorney is still of record." +} - added
Output schema / properties / parties / items / properties / attorneys / items / properties / roleAdded value: +{ + "description": "role_code decoded to a label (e.g., \"Lead attorney\"). Codes 5–9 (\"Self-terminated\" through \"Disbarred\") mean the attorney is no longer of record. The stringified code when upstream sends a value outside the documented enum, \"Unrecorded\" when it sends none.", + "type": "string" +} - added
Output schema / properties / parties / items / properties / attorneys / items / properties / role_code / anyOfAdded value: +[ + { + "type": "number" + }, + { + "type": "null" + } +] - changed
Output schema / properties / parties / items / properties / attorneys / items / properties / role_code / descriptionPrevious value: -"Numeric attorney role code from the party–attorney relationship (e.g., 1 = Lead attorney)."New value: +"Numeric attorney role code from the party–attorney relationship (1 = Attorney to be noticed, 2 = Lead attorney, 3 = Attorney in sealed group, 4 = Pro hac vice, 5 = Self-terminated, 6 = Terminated, 7 = Suspended, 8 = Inactive, 9 = Disbarred, 10 = Unknown); null when upstream recorded no code." - removed
Output schema / properties / parties / items / properties / attorneys / items / properties / role_code / typeRemoved value: -"number" - changed
Output schema / properties / parties / items / properties / attorneys / items / requiredPrevious value: -[ - "attorney_id", - "name", - "contact_raw", - "role_code" -]New value: +[ + "attorney_id", + "name", + "contact_raw", + "role_code", + "role", + "date_action" +] - changed
Output schema / properties / totalCount / descriptionPrevious value: -"Total parties on this docket across all pages."New value: +"Total parties on this docket across all pages — present only when the API reports a numeric count (this endpoint returns it as a URL by default, so it is absent for any list spanning more than one page)." - changed
Output schema / requiredPrevious value: -[ - "docket_id", - "total_parties", - "page", - "next_cursor", - "parties", - "totalCount" -]New value: +[ + "docket_id", + "total_parties", + "page", + "next_cursor", + "parties" +]
5 tool updates
- Changed
courtlistener_get_citations1 field changed- changed
Output schema / properties / results / items / properties / snippet / descriptionPrevious value: -"Text excerpt showing context around the citation (where available)."New value: +"Matched text excerpt from the related opinion, taken from the first opinion variant in the cluster that carries one; empty string when none does. It is a relevance preview for the cluster, not necessarily text surrounding the citation itself."
- Changed
courtlistener_search_dockets15 fields changed- added
Output schema / properties / results / items / properties / attorneysAdded value: +{ + "description": "Attorney names of record on this docket; empty when none are recorded.", + "items": { + "type": "string" + }, + "type": "array" +} - added
Output schema / properties / results / items / properties / case_name_fullAdded value: +{ + "description": "Full case name with all parties; empty string when not recorded.", + "type": "string" +} - removed
Output schema / properties / results / items / properties / document_countRemoved value: -{ - "description": "Number of documents available in RECAP.", - "type": "number" -} - added
Output schema / properties / results / items / properties / firmsAdded value: +{ + "description": "Law firm names of record on this docket; empty when none are recorded.", + "items": { + "type": "string" + }, + "type": "array" +} - added
Output schema / properties / results / items / properties / jurisdiction_typeAdded value: +{ + "description": "Basis of federal jurisdiction (e.g. \"Federal Question\"); empty string when not recorded.", + "type": "string" +} - added
Output schema / properties / results / items / properties / referred_toAdded value: +{ + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ], + "description": "Referred magistrate judge name; null if not recorded." +} - changed
Output schema / properties / results / items / properties / sample_documents / descriptionPrevious value: -"Up to 3 sample filings from this docket."New value: +"Up to 3 sample filings matched on this docket — a search excerpt, not the docket's full filing list. Call courtlistener_get_docket for every entry." - changed
Output schema / properties / results / items / properties / sample_documents / items / properties / date_filed / descriptionPrevious value: -"Date the document was filed."New value: +"Date the parent docket entry was filed; empty string when not recorded." - added
Output schema / properties / results / items / properties / sample_documents / items / properties / document_typeAdded value: +{ + "description": "Document classification (e.g. \"PACER Document\", \"RECAP Document\"); empty string when not recorded.", + "type": "string" +} - added
Output schema / properties / results / items / properties / sample_documents / items / properties / entry_numberAdded value: +{ + "anyOf": [ + { + "type": "number" + }, + { + "type": "null" + } + ], + "description": "Docket entry number this document belongs to; null if unnumbered." +} - added
Output schema / properties / results / items / properties / sample_documents / items / properties / filepath_localAdded value: +{ + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ], + "description": "Fully-qualified RECAP storage URL (https://storage.courtlistener.com/...) for the document; null when no copy is stored." +} - added
Output schema / properties / results / items / properties / sample_documents / items / properties / page_countAdded value: +{ + "anyOf": [ + { + "type": "number" + }, + { + "type": "null" + } + ], + "description": "Page count; null if not recorded." +} - changed
Output schema / properties / results / items / properties / sample_documents / items / requiredPrevious value: -[ - "id", - "description", - "date_filed", - "document_number", - "is_available" -]New value: +[ + "id", + "description", + "date_filed", + "document_number", + "entry_number", + "document_type", + "page_count", + "filepath_local", + "is_available" +] - added
Output schema / properties / results / items / properties / suit_natureAdded value: +{ + "description": "Nature-of-suit label, usually prefixed with its PACER code (e.g. \"830 Patent\"); empty string when not recorded.", + "type": "string" +} - changed
Output schema / properties / results / items / requiredPrevious value: -[ - "docket_id", - "case_name", - "court", - "court_id", - "date_filed", - "date_terminated", - "docket_number", - "pacer_case_id", - "assigned_to", - "cause", - "jury_demand", - "parties", - "document_count", - "sample_documents" -]New value: +[ + "docket_id", + "case_name", + "case_name_full", + "court", + "court_id", + "date_filed", + "date_terminated", + "docket_number", + "pacer_case_id", + "assigned_to", + "referred_to", + "cause", + "jury_demand", + "suit_nature", + "jurisdiction_type", + "parties", + "attorneys", + "firms", + "sample_documents" +]
- Changed
courtlistener_search_judges4 fields changed- changed
Output schema / properties / results / items / properties / aba_rating / descriptionPrevious value: -"ABA qualification ratings."New value: +"ABA qualification labels (e.g. \"Well Qualified\", \"Qualified\"), one per rating on record — not the rating codes." - changed
Output schema / properties / results / items / properties / current_position / anyOfPrevious value: -[ - { - "additionalProperties": false, - "properties": { - "appointer": { - "anyOf": [ - { - "type": "string" - }, - { - "type": "null" - } - ], - "description": "Appointing president; null if elected or not recorded." - }, - "court": { - "anyOf": [ - { - "type": "string" - }, - { - "type": "null" - } - ], - "description": "Court where currently serving; null if not applicable." - }, - "court_id": { - "anyOf": [ - { - "type": "string" - }, - { - "type": "null" - } - ], - "description": "Court identifier." - }, - "date_start": { - "anyOf": [ - { - "type": "string" - }, - { - "type": "null" - } - ], - "description": "Date position started." - }, - "position_type": { - "anyOf": [ - { - "type": "string" - }, - { - "type": "null" - } - ], - "description": "Position title (e.g., \"District Judge\")." - } - }, - "required": [ - "court", - "court_id", - "position_type", - "appointer", - "date_start" - ], - "type": "object" - }, - { - "type": "null" - } -]New value: +[ + { + "additionalProperties": false, + "properties": { + "appointer": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ], + "description": "Name of the appointing president (e.g. \"Obama, Barack Hussein, II\"); null if elected or not recorded." + }, + "court": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ], + "description": "Court full name; null for non-judicial positions." + }, + "court_id": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ], + "description": "Court identifier for use in filter parameters; null for non-judicial positions." + }, + "date_start": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ], + "description": "Date the position started; null if not recorded." + }, + "date_termination": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ], + "description": "Date the position ended; null while the judge still holds it." + }, + "job_title": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ], + "description": "Free-text title for non-judicial roles (e.g. \"Assistant district attorney\"); null for judicial positions." + }, + "organization_name": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ], + "description": "Employer for non-judicial roles; null for judicial positions." + }, + "position_type": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ], + "description": "Judicial position title (e.g. \"Judge\", \"Chief Judge\"); null for non-judicial positions — see job_title." + }, + "selection_method": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ], + "description": "How the judge reached the position (e.g. \"Appointment (President)\", \"Election (Partisan)\"); null if not recorded." + }, + "termination_reason": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ], + "description": "Why the position ended (e.g. \"Appointed to Other Judgeship\", \"Retirement\"); null while still serving." + } + }, + "required": [ + "court", + "court_id", + "position_type", + "job_title", + "organization_name", + "appointer", + "selection_method", + "date_start", + "date_termination", + "termination_reason" + ], + "type": "object" + }, + { + "type": "null" + } +] - changed
Output schema / properties / results / items / properties / current_position / descriptionPrevious value: -"Current or most recent position; null if not available."New value: +"The position with no termination date, or — when several or none qualify — the one with the latest start date. Null when the record carries no positions. courtlistener_get_judge returns the full appointment history." - changed
Output schema / properties / results / items / properties / political_affiliation / descriptionPrevious value: -"Political affiliation codes."New value: +"Party labels (e.g. \"Democratic\", \"Republican\"), one per recorded affiliation — not the single-letter codes the political_affiliation input filter takes."
- Changed
courtlistener_search_opinions3 fields changed- added
Output schema / properties / results / items / properties / opinionsAdded value: +{ + "description": "Opinion variants filed in this case (majority, concurrence, dissent, per curiam). Empty when upstream returned none.", + "items": { + "additionalProperties": false, + "description": "One opinion variant within the cluster.", + "properties": { + "author_id": { + "anyOf": [ + { + "type": "number" + }, + { + "type": "null" + } + ], + "description": "Person ID of the authoring judge — pass to courtlistener_get_judge; null when unattributed." + }, + "cites": { + "description": "Opinion IDs this variant cites. These are opinion-level IDs, not cluster IDs — courtlistener_get_opinion and courtlistener_get_citations both take a cluster_id, so do not pass these values to them directly.", + "items": { + "type": "number" + }, + "type": "array" + }, + "download_url": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ], + "description": "URL of the originating court's copy; null when none was recorded. Often plain HTTP and prone to rot — prefer local_path." + }, + "id": { + "description": "Opinion ID for this variant — identifies one opinion within the cluster (the cluster itself is cluster_id).", + "type": "number" + }, + "local_path": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ], + "description": "CourtListener-hosted copy of the source document (https://storage.courtlistener.com/...); null if not stored." + }, + "per_curiam": { + "description": "True when the opinion was issued per curiam (by the court).", + "type": "boolean" + }, + "type": { + "description": "Variant type as an expanded label (e.g. \"combined-opinion\", \"lead-opinion\", \"dissent\").", + "type": "string" + } + }, + "required": [ + "id", + "type", + "author_id", + "per_curiam", + "download_url", + "local_path", + "cites" + ], + "type": "object" + }, + "type": "array" +} - changed
Output schema / properties / results / items / properties / snippet / descriptionPrevious value: -"Matched text excerpt from the opinion."New value: +"Matched text excerpt, taken from the first entry in opinions[] that carries one; empty string when no variant has an excerpt. CourtListener does not mark which variant the search matched, so treat this as a relevance preview for the cluster, not as an excerpt attributable to a specific opinion — read opinions[] to attribute it." - changed
Output schema / properties / results / items / requiredPrevious value: -[ - "cluster_id", - "case_name", - "case_name_full", - "court", - "court_id", - "date_filed", - "docket_number", - "docket_id", - "citations", - "cite_count", - "judges", - "status", - "snippet" -]New value: +[ + "cluster_id", + "case_name", + "case_name_full", + "court", + "court_id", + "date_filed", + "docket_number", + "docket_id", + "citations", + "cite_count", + "judges", + "status", + "snippet", + "opinions" +]
- Changed
courtlistener_search_oral_arguments2 fields changed- changed
Output schema / properties / results / items / properties / download_url / descriptionPrevious value: -"Direct MP3 download URL; null if not available."New value: +"MP3 URL at the originating court; null if not recorded. Often plain HTTP and prone to rot as courts reorganize — prefer local_path, CourtListener's durable copy." - changed
Output schema / properties / results / items / properties / local_path / descriptionPrevious value: -"Local storage path on CourtListener servers; null if not available."New value: +"CourtListener-hosted copy of the recording (https://storage.courtlistener.com/...); null if not stored."
2 tool updates
- Changed
courtlistener_lookup_courts4 fields changed- added
Input schema / properties / pageAdded value: +{ + "default": 1, + "description": "Page number (1-indexed). CourtListener caps /courts/ at ~20 rows per page regardless of size, so the full list (~472 courts) spans ~24 pages — pass the next_cursor from a previous response here to page through them.", + "maximum": 9007199254740991, + "minimum": 1, + "type": "integer" +} - added
Output schema / properties / next_cursorAdded value: +{ + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ], + "description": "Next page number to pass as the `page` argument (this list is page-paginated at ~20 rows/page); null when this is the last page." +} - added
Output schema / properties / pageAdded value: +{ + "description": "Current page number (1-indexed).", + "type": "number" +} - changed
Output schema / requiredPrevious value: -[ - "courts", - "totalCount" -]New value: +[ + "page", + "next_cursor", + "courts", + "totalCount" +]
- Changed
courtlistener_search_financial_disclosures1 field changed- changed
Input schema / properties / year / descriptionPrevious value: -"Filing year to filter by (e.g., 2022). Filters the fetched filings — pair with judge_id for complete per-judge results. Omit to return all available years."New value: +"Filing year to filter by (e.g., 2022). Applied client-side to the fetched page only — CourtListener rejects a server-side year param, so filings for this year on later pages are not included. When a page has no match for the year but more pages remain, next_cursor is returned; pass it as cursor to check the next page. Omit to return all years on the page."
5 tool updates
- Changed
courtlistener_lookup_citation1 field changed- removed
Input schema / properties / citation / minLengthRemoved value: -1
- Changed
courtlistener_search_dockets1 field changed- removed
Input schema / properties / q / minLengthRemoved value: -1
- Changed
courtlistener_search_judges1 field changed- removed
Input schema / properties / q / minLengthRemoved value: -1
- Changed
courtlistener_search_opinions1 field changed- removed
Input schema / properties / q / minLengthRemoved value: -1
- Changed
courtlistener_search_oral_arguments1 field changed- removed
Input schema / properties / q / minLengthRemoved value: -1
1 tool update
- Added
courtlistener_get_financial_disclosure
3 tool updates
- Changed
courtlistener_get_citations2 fields changed- changed
Input schema / properties / page_size / defaultPrevious value: -10New value: +20 - changed
Input schema / properties / page_size / descriptionPrevious value: -"Number of results (1–20). Each citation tool call costs one request against the rate limit — keep page_size low for multi-hop traversal."New value: +"Number of results to request (default 20). For direction=\"cited_by\", CourtListener enforces a minimum of 20 results per page regardless of the value passed — you will always receive at least 20 results. direction=\"citing\" returns at most page_size (the cited-opinion list is sliced before querying) — fewer when the opinion cites fewer than page_size distinct opinions. Each citation tool call costs one request against the rate limit — keep low for multi-hop traversal."
- Changed
courtlistener_get_docket6 fields changed- added
Input schema / properties / entries_pageAdded value: +{ + "default": 1, + "description": "Page of docket entries to fetch (1-indexed). Docket entries are page-paginated at 20 per page; pass the next_cursor from a previous response here to page through large cases.", + "maximum": 9007199254740991, + "minimum": 1, + "type": "integer" +} - changed
Input schema / properties / entries_page_size / descriptionPrevious value: -"Number of docket entries to return (1–50). Large cases can have hundreds of entries."New value: +"Requested docket entries per page. NOTE: CourtListener ignores this value — /docket-entries/ always returns a fixed 20-entry page regardless of what is passed. Use entries_page to reach entries beyond the first 20 (large cases can have hundreds)." - changed
Output schema / properties / entries / descriptionPrevious value: -"Docket entries up to entries_page_size."New value: +"Docket entries for this page (fixed at 20 per page; entries_page_size is not honored by upstream)." - added
Output schema / properties / entries_pageAdded value: +{ + "description": "Current entries page number (1-indexed).", + "type": "number" +} - added
Output schema / properties / next_cursorAdded value: +{ + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ], + "description": "Next page number to pass as the `entries_page` argument (docket entries are page-paginated); null when this is the last page." +} - changed
Output schema / requiredPrevious value: -[ - "docket_id", - "case_name", - "case_name_full", - "court", - "court_id", - "date_filed", - "date_terminated", - "docket_number", - "pacer_case_id", - "assigned_to", - "referred_to", - "cause", - "jury_demand", - "jurisdiction_type", - "total_entries", - "entries" -]New value: +[ + "docket_id", + "case_name", + "case_name_full", + "court", + "court_id", + "date_filed", + "date_terminated", + "docket_number", + "pacer_case_id", + "assigned_to", + "referred_to", + "cause", + "jury_demand", + "jurisdiction_type", + "total_entries", + "entries_page", + "next_cursor", + "entries" +]
- Changed
courtlistener_search_financial_disclosures1 field changed- changed
Input schema / properties / page_size / descriptionPrevious value: -"Number of filings to return (1–20)."New value: +"Number of filings to request (default 20). CourtListener enforces a minimum of 20 results per page regardless of the value passed — you will always receive at least 20 filings."
2 tool updates
- Changed
courtlistener_get_opinion6 fields changed- added
Input schema / properties / sectionsAdded value: +{ + "description": "Opinion variant identifiers to retrieve in full, from a prior outline response (e.g. [\"opinion_12345\"]). Omit to return all variants, or an outline if they overflow the inline byte budget.", + "items": { + "type": "string" + }, + "type": "array" +} - added
Output schema / properties / kindAdded value: +{ + "description": "'full' returns the opinion variants (all, or a selected subset); 'outline' lists each variant as a retrievable section (opinion_<id>) when the opinions overflow the inline byte budget. Cluster metadata is present either way.", + "enum": [ + "full", + "outline" + ], + "type": "string" +} - changed
Output schema / properties / opinions / descriptionPrevious value: -"All opinion variants within this cluster."New value: +"All opinion variants within this cluster. Present in full mode; omitted in outline mode — re-call with sections:[\"opinion_<id>\"] to retrieve specific variants." - added
Output schema / properties / retrieval_noticeAdded value: +{ + "description": "How to re-call the tool for specific opinion variants when the opinions overflow.", + "type": "string" +} - added
Output schema / properties / sectionsAdded value: +{ + "description": "Retrievable opinion variants, largest first — pass names to `sections` on a re-call.", + "items": { + "additionalProperties": false, + "description": "A retrievable opinion variant (opinion_<id>) and its serialized byte size.", + "properties": { + "bytes": { + "description": "Serialized byte size of the section", + "maximum": 9007199254740991, + "minimum": 0, + "type": "integer" + }, + "name": { + "description": "Section identifier — pass in `sections` to retrieve it", + "type": "string" + } + }, + "required": [ + "name", + "bytes" + ], + "type": "object" + }, + "type": "array" +} - changed
Output schema / requiredPrevious value: -[ - "cluster_id", - "case_name", - "case_name_full", - "court", - "court_id", - "date_filed", - "docket_id", - "docket_number", - "judges", - "citations", - "cite_count", - "precedential_status", - "syllabus", - "posture", - "opinions" -]New value: +[ + "cluster_id", + "case_name", + "case_name_full", + "court", + "court_id", + "date_filed", + "docket_id", + "docket_number", + "judges", + "citations", + "cite_count", + "precedential_status", + "syllabus", + "posture", + "kind" +]
- Changed
courtlistener_get_oral_argument5 fields changed- added
Input schema / properties / sectionsAdded value: +{ + "description": "Section identifiers to retrieve in full, from a prior outline response (e.g. [\"transcript\"]). Omit for the full record, or an outline if it overflows the inline budget.", + "items": { + "type": "string" + }, + "type": "array" +} - added
Output schema / properties / kindAdded value: +{ + "description": "'full' returns the record (or the selected sections); 'outline' lists retrievable sections when the transcript overflows the inline byte budget.", + "enum": [ + "full", + "outline" + ], + "type": "string" +} - added
Output schema / properties / retrieval_noticeAdded value: +{ + "description": "How to re-call the tool for specific sections when the record overflows.", + "type": "string" +} - added
Output schema / properties / sectionsAdded value: +{ + "description": "Retrievable sections, largest first — pass names to `sections` on a re-call.", + "items": { + "additionalProperties": false, + "description": "A retrievable section of the record and its serialized byte size.", + "properties": { + "bytes": { + "description": "Serialized byte size of the section", + "maximum": 9007199254740991, + "minimum": 0, + "type": "integer" + }, + "name": { + "description": "Section identifier — pass in `sections` to retrieve it", + "type": "string" + } + }, + "required": [ + "name", + "bytes" + ], + "type": "object" + }, + "type": "array" +} - changed
Output schema / requiredPrevious value: -[ - "oral_argument_id", - "case_name", - "case_name_full", - "docket_id", - "duration_seconds", - "download_url", - "judges", - "panel_ids", - "has_transcript", - "transcript" -]New value: +[ + "kind" +]
2 tool updates
- Changed
courtlistener_get_judge2 fields changed- changed
Output schema / properties / positions / items / properties / appointer / descriptionPrevious value: -"Appointing president name; null if elected or not recorded."New value: +"Position URI of the appointing authority (e.g., \".../positions/123/\"), not resolved to a name; null if elected or not recorded." - changed
Output schema / properties / positions / items / properties / nomination_process / descriptionPrevious value: -"Nomination process; null if not recorded."New value: +"Selection method, expanded to a readable label (e.g., \"Appointment (President)\"); null if not recorded."
- Changed
courtlistener_get_opinion1 field changed- changed
Output schema / properties / opinions / items / properties / html_text / descriptionPrevious value: -"Full opinion text as HTML; may be empty if only a download URL is available."New value: +"Full opinion text as HTML, drawn from the best available variant (citation-linked when present); empty only when no HTML text is stored — use download_url then."
2 tool updates
- Changed
courtlistener_get_docket3 fields changed- changed
Output schema / properties / entries / items / properties / documents / items / properties / document_number / anyOfPrevious value: -[ - { - "type": "number" - }, - { - "type": "null" - } -]New value: +[ + { + "type": "string" + }, + { + "type": "null" + } +] - changed
Output schema / properties / entries / items / properties / documents / items / properties / document_number / descriptionPrevious value: -"PACER document number; null if not assigned."New value: +"PACER document number as a string (e.g. \"1\"); attachments can be non-integer like \"70-1\". Null if not assigned." - changed
Output schema / properties / entries / items / properties / documents / items / properties / filepath_local / descriptionPrevious value: -"RECAP storage URL for available documents; null if not available."New value: +"Fully-qualified RECAP storage URL (https://storage.courtlistener.com/...) for the document; null if not available."
- Changed
courtlistener_get_parties4 fields changed- changed
Output schema / properties / next_cursor / descriptionPrevious value: -"Opaque cursor for the next page; null when this is the last page."New value: +"Next page number to pass as the `page` argument (this list is page-paginated); null when this is the last page." - added
Output schema / properties / total_parties / anyOfAdded value: +[ + { + "type": "number" + }, + { + "type": "null" + } +] - changed
Output schema / properties / total_parties / descriptionPrevious value: -"Total number of parties on this docket across all pages."New value: +"Total parties on this docket across all pages; null when upstream reports no count (a multi-page list whose total is unknown until the last page)." - removed
Output schema / properties / total_parties / typeRemoved value: -"number"
Related MCP Connectors
Search US federal and state court records through CourtListener and the RECAP archive
MCP for CourtListener: US federal and state opinions, dockets, judges, plus eCFR regulations.
Search public U.S. federal litigation: companies, cases, dockets and document metadata.
Search a large legal database of 325M+ US court records: cases, attorneys, judges and courts.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceEnables legal research across 3,352 U.S. courts using the CourtListener API, providing access to case search, precedent analysis, judge patterns, citation validation, and federal PACER dockets through natural language queries.6 npm3MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to query and access legal data from the Free Law Project's CourtListener API, including court opinions, judges, and dockets, with basic access requiring no authentication.62 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables users to search and retrieve court docket records across US state, county, and federal courts, including PACER party searches, and to get full case details.47 npmMIT
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd
Glama MCP Gateway
Add one secure layer between your agents and this server.