Skip to main content
Glama

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, and the description adds genuinely new context: the upstream source (CourtListener, 60M+ opinions), per-call cost, and a cryptographic attestation/verification path. It does not describe result ordering beyond 'relevance' or any rate limits, but the added operational context is substantive.

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 purpose is front-loaded and readable, but the pricing is stated twice ('$0.50' and '$0.50 USDC per call') and the attestation/verification sentence is marketing padding that dilutes the operational content.

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 zero parameter documentation, the description should carry more weight; it partially covers return fields (citation counts, court, precedential status) but leaves all four input parameters and result pagination/limit behavior unexplained.

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 must compensate and largely does not. It only implies that 'topic' is the legal subject; court format, limit bounds, and date_after syntax are left entirely to the bare schema.

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 names the return payload (top cases by relevance with citation counts, court, precedential status). It does not, however, distinguish itself from the sibling get_federal_case_law, leaving the agent to guess which to call.

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?

Offers use-case framing ('legal research agents, litigation intelligence, and compliance gap analysis'), which implies when the tool fits, but gives no explicit when-not conditions and no comparison to the closely named sibling get_federal_case_law.

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