Skip to main content
Glama

get_federal_court_cases

Read-only

Use when screening a company, executive, vendor, or counterparty for federal litigation exposure before a contract award, acquisition, investment, board appointment, or enterprise partnership. Returns active and historical federal court dockets across all US district and appellate courts — case names, docket numbers, courts, filing dates, nature of suit, and active status. Example: Acme Corp — 4 active federal cases: patent infringement N.D. Cal. (filed 2023), FLSA collective action S.D.N.Y. with 847 plaintiffs (filed 2023), FTC antitrust investigation D.D.C. (filed 2024), securities class action S.D.N.Y. (filed 2024) — aggregate litigation liability exposure estimated above $200M. Source: CourtListener, 1M+ federal court documents. $0.50 USDC per call.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "party_name": "<party_name>"
    },
    "name": "get_federal_court_cases"
  }
}

Input Schema

NameRequiredDescriptionDefault
courtNoCourt identifier e.g. ca9, scotus, dcd, nyed, ndca
party_nameYes
years_backNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Adds substantial context beyond the read-only/open-world annotations: the data source (CourtListener, 1M+ documents), the cost of $0.50 USDC per call, and the coverage scope of all federal district and appellate courts. It does not disclose result caps, pagination, or how party-name matching works, which matters for a paid open-world query.

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

Conciseness3/5

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

Usage context is correctly front-loaded and the source/cost line is essential for a paid tool. However, the Acme Corp example runs long, including an estimated $200M liability figure that illustrates outcome value but does not help the agent select or invoke the tool correctly.

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 no output schema, the description carries the burden of describing return values and does so by enumerating case names, docket numbers, courts, filing dates, nature of suit, and active status. Missing only operational details such as how many results come back and whether a court filter is required for reasonable performance.

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 only 33%, so the description must compensate. It partly does — 'all US district and appellate courts' implies the court param is an optional narrowing filter, and the example shows a company name for party_name — but years_back (default 5) and party_name matching behavior are never explained.

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 concrete verb and resource — returns active and historical federal court dockets across all US district and appellate courts — plus the exact fields returned. It does not explicitly differentiate itself from the similarly named sibling get_federal_case_law, leaving the agent to infer that 'dockets' means filings rather than opinions.

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?

Opens with a clear when-to-use trigger: screening a company, executive, vendor, or counterparty for litigation exposure before an award, acquisition, investment, board appointment, or partnership. No when-not conditions or named alternatives are given, so the agent still has to guess whether another tool covers related legal screening.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources