Skip to main content
Glama

Stratalize Intelligence

Get Litigation Enforcement Snapshot

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

A3.9/5.0
Behavior4/5

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

Adds real behavior beyond the readOnly/openWorld/destructive annotations: partial degradation per section when a source is unavailable, a named dependency (CourtListener) for alerts, and a per-call price of $3.00 USDC. Return shape and latency are not described, and there is no output schema to compensate.

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?

Three tight sentences that front-load the trigger condition, then the composition, then the input/cost facts. The 'Input party_name (required)' fragment slightly repeats what the schema already enforces, but it is short and placed at the end where it does not obstruct scanning.

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?

The composite nature, degradation semantics, dependency, and pricing are well covered, which matters for a fan-in tool. However, with no output schema and four of five parameters unexplained, an agent cannot confidently scope the request (e.g., whether to pass days_back or institution_name) before paying $3.00.

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?

Five parameters exist with 0% schema description coverage, and the description only identifies party_name as required. The roles of court, days_back (with its 1-90 bounds), company_name, and institution_name — and how they interact with party_name — are undocumented in both the schema and the prose, leaving the agent to guess.

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 aggregation verb ('fans in') and enumerates the exact resources composited: litigation risk composite, new litigation alerts, federal court cases, FTC enforcement history, and OCC enforcement actions. This makes clear it is a fan-in snapshot rather than one of the single-source siblings like get_ftc_enforcement_history or get_occ_enforcement_actions.

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?

The opening clause gives a concrete use case: assessing litigation and enforcement exposure for a counterparty. It does not explicitly tell the agent when to prefer a single-source sibling (e.g., get_party_litigation_profile) over this composite, or when the added cost is unjustified, so guidance is clear but not exhaustive.

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