Skip to main content
Glama

Stratalize Intelligence

Get Federal Court Cases

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

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, destructiveHint=false, so the safety profile is covered. The description adds genuinely new behavioral facts: the upstream source (CourtListener, 1M+ federal court documents) and a per-call price of $0.50 USDC, which an agent must know before invoking. It does not discuss rate limits, result caps, or pagination, 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.

Conciseness3/5

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

The usage trigger is correctly front-loaded, but the four-item worked example with plaintiff counts and an "aggregate litigation liability exposure estimated above $200M" figure consumes roughly half the text. That example does useful work as a stand-in for the missing output schema, but the liability estimate is illustrative flourish that does not help an agent call the tool.

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 is the only place an agent learns the return shape, and the worked example plus the explicit field list covers that well; pricing and data source are also disclosed. What is missing is operational detail — how party_name is matched, how the court filter and years_back interact, and whether results are bounded or paginated.

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% — court is documented, party_name and years_back are not. The description partially compensates by showing a party_name example ("Acme Corp") and by saying results are "active and historical," which implies what years_back controls. It never explains matching semantics for party_name (exact vs fuzzy, legal entity naming) or the meaning of the years_back default of 5, so a real gap remains.

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: it screens a named party and returns active and historical federal court dockets across all US district and appellate courts. The field list (case names, docket numbers, courts, filing dates, nature of suit, active status) makes clear this is litigation-docket retrieval, not case-law text retrieval, which distinguishes it from sibling get_federal_case_law.

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 when screening a company, executive, vendor, or counterparty for federal litigation exposure before a contract award, acquisition, investment, board appointment, or enterprise partnership" gives a concrete trigger context and names the subject types it applies to. It stops short of naming an alternative tool or stating when-not to use it, so it lands at a clear 4 rather than a 5.

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