Skip to main content
Glama

get_new_litigation_alerts

Read-only

Use when monitoring new federal dockets filed against a party in the last N days. Returns docket alerts from CourtListener; zero results is a legitimate empty answer. Source: CourtListener docket search. $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_new_litigation_alerts"
  }
}

Input Schema

NameRequiredDescriptionDefault
courtNo
days_backNo
party_nameYes
nature_of_suitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Beyond the read-only/open-world annotations, the description discloses the data source, that zero results is a legitimate empty answer, and a per-call cost. It does not discuss pagination, rate limits, or latency, but it adds useful behavioral context that annotations do not cover.

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?

The definition is four short sentences with no repetition or filler. The usage condition is front-loaded, followed by behavior, source, and cost, all of which earn their place.

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?

For a four-parameter, open-world search with no output schema, the description covers source, empty-result behavior, and cost. However, it leaves two filter parameters semantically unexplained, which is a meaningful gap for correct invocation.

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 compensate for undocumented parameters. It explains the party and recent-days concepts but says nothing about the court or nature_of_suit filters, nor does it clarify acceptable formats or the 90-day maximum.

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 description states a specific verb and resource: monitoring new federal dockets filed against a party in the last N days, returning CourtListener docket alerts. It is distinguishable from broader litigation-profile or risk-composite siblings, though it does not explicitly name alternatives.

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 usage context: use when monitoring new federal dockets against a party within a recent window. It does not state when not to use it or name alternative tools for broader litigation analysis, but the intended scenario is clear.

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