Skip to main content
Glama

Stratalize Intelligence

Get Docket Intelligence

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

B3.4/5.0
Behavior4/5

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

Beyond the annotations (readOnlyHint, openWorldHint, destructiveHint false), the description discloses the upstream data source (CourtListener), the filtering behavior (open cases only), and the per-call cost of $0.10 USDC. The attestation and verification URL add provenance context the annotations do not carry. Remaining gaps are output size, pagination, and latency behavior.

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?

The purpose and returned fields are front-loaded in the first clause, and each subsequent sentence adds something (source, use case, coverage, provenance, price). The attestation/verification clause is boilerplate-ish but short, and nothing is duplicated.

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 no output schema, the description does well to enumerate returned fields and the data source. However, for a two-parameter tool at 0% schema coverage it leaves the court parameter undefined and says nothing about result cardinality, pagination, or whether the filter narrows or summarizes dockets.

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%, so the description must carry parameter meaning. 'For a named party' maps to party_name, but the second parameter, 'court' (string, maxLength 50), is never explained — whether it is a filter, expects a court ID vs. name, and how 'most active courts' relates to it are all unstated.

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?

The opening clause names a specific resource (active federal dockets), the entity (a named party), and enumerates the returned fields (last filing date, nature of suit, most active courts), plus the data source (CourtListener). It is clear what the tool does, though differentiation from sibling intelligence tools rests mostly on the name rather than the text.

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 litigation is out of scope. There is no explicit when-not guidance and no named alternative for closed-case or full docket-history lookups, so the agent must infer the boundary.

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