Skip to main content
Glama

Stratalize Intelligence

Get Party Litigation Profile

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 cover read-only, open-world, non-destructive, so the lower bar applies. The description still adds real context: upstream source (CourtListener), a per-call price of $0.10 USDC, and an attestation/verification mechanism. What it lacks is failure behavior (e.g. no-match cases) and any rate or freshness detail.

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 sentence is well front-loaded and informative, but the opening tagline ('governed intelligence for the agentic economy') earns nothing, and the attestation/verification sentence is marketing rather than selection-relevant. Sizing is acceptable but padded.

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-only tool with no output schema, the description covers what the response will contain, the data source, and the cost model. Gaps remain around lookup semantics and empty-result behavior, but nothing essential to invoking it is missing.

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 should compensate more than it does; it only restates that the parameter is a party name. It does add the meaningful clarification that the party may be a company or an individual, but gives no matching semantics (exact vs fuzzy, formatting, aliases).

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 resource and scope: 'Federal litigation history for a company or individual', then enumerates the contents (total docket count, active courts, nature of suit breakdown, recent cases). It does not explicitly distinguish itself from close siblings like get_litigation_risk_composite or get_litigation_enforcement_snapshot, so it stops short of a 5.

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 guidance beyond 'Required param: party name'. Nothing tells the agent when to prefer this over the litigation siblings or what prerequisites/limits apply. The cost line hints at a pay-per-call tradeoff but is not framed as usage 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