Skip to main content
Glama

get_party_litigation_profile

Read-only

Stratalize — governed intelligence for the agentic economy. Federal litigation history for a company or individual — total docket count, active courts, nature of suit breakdown, and recent cases. Required param: party name. Source: CourtListener. Cryptographically attested with a post-quantum signed settlement receipt. Verify at trust.stratalize.com/verify. $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_party_litigation_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
party_nameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, and non-destructive behavior, so safety is covered. The description adds genuinely useful non-schema context: the upstream source (CourtListener), a per-call price of $0.10 USDC, and an attestation/verification mechanism — behavioral facts an agent cannot get from the schema. It does not describe error or rate-limit behavior, keeping it below 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core capability sentence is well front-loaded, but the leading brand tagline 'governed intelligence for the agentic economy' is pure marketing filler, and the cryptographic-attestation and pricing boilerplate consumes a third of the text. What remains relevant is fine, but the signal-to-noise ratio is weakened.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single-parameter read tool with no output schema, the description adequately covers what is returned (docket count, courts, suit breakdown, recent cases), the data source, and the cost. Missing pagination/recency semantics for 'recent cases' is a minor gap given the tool's simplicity.

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 description coverage is 0%, so the description must compensate, and it does only minimally by restating 'Required param: party name' — which merely repeats the schema's required field. It adds no format guidance (company vs. individual naming, legal entity suffixes, ticker alternatives) that would help the agent construct a valid value.

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 names a specific verb and resource ('Federal litigation history for a company or individual') and enumerates the returned facets: total docket count, active courts, nature of suit breakdown, recent cases. It does not explicitly distinguish itself from litigation-adjacent siblings such as get_litigation_risk_composite or get_litigation_enforcement_snapshot, but the resource scope is unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use or when-not-to-use guidance, and no alternative is named despite several litigation-related siblings existing. The agent must infer usage purely from the phrase 'litigation history', which is context but not routing guidance.

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