Skip to main content
Glama

get_litigation_risk_composite

Read-only

Use when synthesizing litigation risk from party profile, docket intelligence, and optional judge analytics. Composite degrades transparently when partial CourtListener sources fail. Source: CourtListener composite. $0.50 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_risk_composite"
  }
}

Input Schema

NameRequiredDescriptionDefault
judge_nameNo
party_nameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, openWorld, non-destructive), so the description's added value is in disclosing graceful degradation when partial CourtListener sources fail and the $0.50 USDC per-call cost. Those are real operational facts an agent needs before committing. It stops short of saying what a degraded response looks like.

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 short sentences, front-loaded with the trigger condition, then degradation behavior, then cost and source. Nearly every clause earns its place; the trailing 'Source: CourtListener composite' partially repeats the earlier CourtListener reference.

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 and a composite, multi-source tool, the description should say more about what the returned risk assessment contains and how degradation is surfaced. Cost and failure behavior are covered, but the shape of the result and party-name format are not.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so the description must carry parameter meaning. It partially does: 'party profile' maps to party_name and 'optional judge analytics' signals that judge_name is not required. However, it gives no format guidance for party_name (full legal name vs. short name) or what judge_name accepts.

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 (synthesizing) and resource (litigation risk composite) and enumerates its constituent inputs: party profile, docket intelligence, optional judge analytics. This differentiates it from single-signal siblings like get_party_litigation_profile, though it never names an alternative directly.

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?

The opening 'Use when synthesizing litigation risk from...' gives a clear triggering context, so usage is implied rather than spelled out. It provides no explicit when-not conditions or routing to sibling tools such as get_litigation_enforcement_snapshot when a narrower signal is wanted.

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