Skip to main content
Glama

Stratalize Intelligence

Get New Litigation Alerts

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?

Annotations already cover read-only, open-world, non-destructive status, and the description adds genuinely useful operational context beyond them: results come from CourtListener, zero results is a legitimate empty answer (not a failure), and each call costs $0.10 USDC. It stops short of describing pagination or result ordering, which matters for a docket search.

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?

Three short sentences with the trigger condition front-loaded, followed by source, empty-result semantics, and cost. Every sentence carries information an agent would otherwise have to guess at; nothing is padded or repeated.

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 correctly covers return-shape essentials (docket alerts, empty results valid) and cost, and annotations handle the safety profile. The remaining gap is functional: the coverage of what the optional court and nature_of_suit filters actually do is missing, which limits correct invocation on anything but the minimal required-parameter call.

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% and the description only obliquely implies two of the four parameters ('party' and 'last N days'). The court and nature_of_suit filters, the 1-90 day bound on days_back, and the string length limits on party_name are documented nowhere in either the schema or the description, so the agent must infer filtering capability from parameter names alone.

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 specific verb and resource: monitoring new federal dockets filed against a party within the last N days, and names the data source (CourtListener docket search). An agent can tell this is a recent-filing alert feed rather than a risk score or party profile, though it does not explicitly distinguish itself from similarly named litigation siblings.

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 an explicit trigger condition ('Use when monitoring new federal dockets filed against a party in the last N days'), which is clear actionable context. It does not state when NOT to use it or name an alternative sibling for broader/summary litigation queries, so the routing guidance is one-sided.

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