Skip to main content
Glama

Stratalize Intelligence

Get Case Law Synthesis

get_case_law_synthesis
Read-only

Federal case law synthesis across US courts via CourtListener. Returns top cases by relevance for a legal topic with citation counts, court, and precedential status. Use for legal research agents, litigation intelligence, and compliance gap analysis. Source: CourtListener 60M+ opinions. $0.50. Cryptographically attested with a post-quantum signed settlement receipt. Verify at trust.stratalize.com/verify. $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": {
      "topic": "<topic>"
    },
    "name": "get_case_law_synthesis"
  }
}

Input Schema

NameRequiredDescriptionDefault
courtNo
limitNo
topicYes
date_afterNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/5.0
Behavior4/5

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

Annotations already declare readOnly/openWorld/non-destructive, so the description's main added value is disclosing that this is a paid call ($0.50 USDC per call), the source (CourtListener 60M+ opinions), and the attestation/verification path. That cost-and-provenance information is genuinely useful context an agent cannot get from annotations, though it says nothing about rate limits or result ordering beyond 'top cases by relevance'.

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?

Core capability is front-loaded in the first two sentences, but the definition then wastes space on marketing boilerplate ('Cryptographically attested with a post-quantum signed settlement receipt', verification URL) and repeats the price twice ('$0.50' and '$0.50 USDC per call'). Pricing deserves one mention; the attestation pitch does not earn its place in a tool selection definition.

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?

There is no output schema, so the description appropriately summarizes what comes back, and the paid nature is disclosed. However, for a four-parameter tool with zero schema descriptions, the absence of any guidance on the 'court' identifier format or date filtering leaves real gaps an agent would hit on first invocation.

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 four parameters, so the description carries the full burden and largely fails: only 'topic' is implied by 'for a legal topic'. The format of 'court' (name? CourtListener court ID?), the meaning of 'limit' (max 20), and the 'date_after' YYYY-MM-DD semantics are never explained.

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 and resource ('Federal case law synthesis across US courts via CourtListener') and even previews the return payload (citation counts, court, precedential status). It does not explicitly contrast itself with the sibling get_federal_case_law, so the boundary between 'synthesis' and plain case-law retrieval is left for the agent to infer.

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 description names audiences and scenarios ('legal research agents, litigation intelligence, and compliance gap analysis'), which implies usage but never states when to prefer this over get_federal_case_law or get_citation_authority. No exclusions, prerequisites, or alternatives are given, leaving routing decisions to inference.

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