Skip to main content
Glama

Stratalize Intelligence

Get Federal Case Law

get_federal_case_law
Read-only

Federal court opinion search — keyword or party name search with citation counts, court, date, and excerpt. Optional court filter (e.g. scotus, ca2, dcd). 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": {
      "query": "<query>"
    },
    "name": "get_federal_case_law"
  }
}

Input Schema

NameRequiredDescriptionDefault
courtNo
queryYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true and destructiveHint=false, so safety is covered. The description adds real context beyond that: the upstream source (CourtListener), a per-call price ($0.10 USDC), and a verification mechanism with a URL — commercially relevant behavior an agent otherwise could not know. It omits result limits/pagination, keeping it from a 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 purpose and parameters are front-loaded and the em-dash structure reads well, but 'Cryptographically attested with a post-quantum signed settlement receipt' plus the verify URL is marketing framing that does not help an agent decide or call correctly, diluting an otherwise tight paragraph.

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?

With no output schema, the description supplies the return fields itself and adds source, cost, and attestation details. For a two-parameter read-only search tool that is close to complete; only result-count/pagination behavior is unaddressed.

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

Parameters5/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, and it does: 'query' is characterized as keyword or party name (with a 2-500 char shape in schema), and 'court' is explained as an optional filter with valid-value examples (scotus, ca2, dcd). That is a meaningful lift over a bare maxLength constraint.

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?

Names a specific verb and resource: 'Federal court opinion search', and states the two search modes (keyword or party name) plus the fields returned (citation counts, court, date, excerpt). It does not distinguish itself from plausible siblings such as get_federal_court_cases or get_citation_authority, 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 Guidelines3/5

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

Usage is implied by 'keyword or party name search' and the optional court filter with concrete codes (scotus, ca2, dcd), but there is no explicit when-to-use/when-not guidance and no named alternative for overlapping case-law lookups.

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