Skip to main content
Glama

get_docket_intelligence

Read-only

Active federal dockets for a named party — open cases only, last filing date, nature of suit, and most active courts. Source: CourtListener. Use for ongoing litigation monitoring. Cryptographically attested with a post-quantum signed settlement receipt. Verify at trust.stratalize.com/verify. $0.10 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_docket_intelligence"
  }
}

Input Schema

NameRequiredDescriptionDefault
courtNo
party_nameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnly=true, destructive=false and openWorld=true, so the safety profile is covered. The description still adds real context beyond them: the CourtListener data source, the hard filter to open cases only (a result-shaping constraint), an explicit per-call cost of $0.10 USDC, and an attestation/verification path. It does not describe pagination, result caps, or empty-result behavior.

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 first two sentences are front-loaded and efficient. The attestation clause ("Cryptographically attested with a post-quantum signed settlement receipt. Verify at trust.stratalize.com/verify.") is verbose and, for a docket lookup, reads as boilerplate — the pricing line plausibly earns its place, but the receipt wording does not.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With only two parameters, no output schema, and annotations carrying safety, the description is close to sufficient: it names the return fields and the data source. The gaps are the unexplained court filter and no statement about result limits or behavior when no open dockets match.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% on two parameters, so the description must carry the load. "For a named party" loosely maps to party_name, but the court parameter is never mentioned and no format guidance is given for either field (e.g., court identifier style, full vs. partial party names, min/max length implications). Half the parameter surface stays undocumented.

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?

"Active federal dockets for a named party" states a specific resource and scope, and the follow-up clause enumerates exactly what comes back (open cases only, last filing date, nature of suit, most active courts). The source (CourtListener) is named, so an agent knows precisely what corpus this queries rather than guessing among the many sibling intelligence tools.

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?

"Use for ongoing litigation monitoring" gives one positive use case, and "open cases only" implicitly signals that closed/historical matters are out of scope. However, no alternative tool is named, no when-not-to-use condition is given, and nothing says what to do if the party name is ambiguous or matches multiple entities.

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