Skip to main content
Glama

get_litigation_enforcement_snapshot

Read-only

Use when assessing litigation and enforcement exposure for a counterparty. Fans in litigation risk composite, new litigation alerts, federal court cases, FTC enforcement history, and OCC enforcement actions — degrading per-section (including CourtListener-dependent alerts) on source_unavailable. Input party_name (required). $3.00 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_litigation_enforcement_snapshot"
  }
}

Input Schema

NameRequiredDescriptionDefault
courtNo
days_backNo
party_nameYes
company_nameNo
institution_nameNo

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 cover the safety profile (readOnly, non-destructive, open-world), so the description earns credit for adding non-obvious behavior: per-section degradation on source_unavailable, specifically that CourtListener-dependent alerts are affected, plus a $3.00 USDC per-call price. What it does not disclose is the response shape or latency profile, which matters for a paid multi-source fan-out with no output schema.

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 tightly packed sentences: trigger condition first, then the fanned-in sources, then degradation behavior, required input and price. Every clause carries distinct information and nothing is repeated from the annotations or schema.

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?

Naming the five constituent sections effectively communicates the return shape despite there being no output schema, which is genuinely useful. However, for a five-parameter aggregation tool with 0% schema coverage, leaving four parameters entirely unexplained is a meaningful completeness gap for an agent trying to scope the call correctly.

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% across five parameters, so the description carries the full burden — yet it only confirms party_name as required. The court, days_back, company_name and institution_name parameters are never mentioned, and there is no guidance on precedence between party_name, company_name and institution_name or on what days_back governs in an enforcement-history context.

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 — fans in litigation risk composite, new litigation alerts, federal court cases, FTC enforcement history and OCC enforcement actions into one snapshot for a counterparty. Because it enumerates the exact sibling tools it aggregates, an agent can distinguish it from get_litigation_risk_composite or get_ftc_enforcement_history without opening any schema.

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 assessing litigation and enforcement exposure for a counterparty" gives a clear triggering context, and the enumeration of constituent sources implies this is the aggregate rather than single-source route. It does not explicitly say when to prefer the individual sibling tools over this one, nor does it name exclusions, so it falls short of the top score.

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