Skip to main content
Glama

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.5/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 adds genuinely new behavioral facts: the upstream source (CourtListener), a per-call price ($0.10 USDC), and a cryptographic settlement receipt with a verification URL. That cost and provenance disclosure is information an agent cannot get from the schema or annotations. It does not mention rate limits, pagination, or result caps, which keeps it below 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.

Conciseness4/5

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

Front-loaded with purpose, then returned fields, then the optional filter, then source/cost/attestation. It is compact for the amount of content conveyed; the attestation and payment boilerplate is slightly promotional but is arguably functional context.

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?

For a two-parameter read-only search with no output schema, the description covers purpose, returned fields, data source, and price, which is nearly enough. What is missing is anything about result volume, ranking, or pagination behavior — an agent cannot tell how many opinions come back or how to page.

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

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description carries the full burden, and it does compensate well: it explains that 'query' supports keyword or party-name search and that 'court' is an optional filter with concrete jurisdiction codes (scotus, ca2, dcd). It adds no length/format guidance (e.g. the 2–500 char bounds) but the semantics of both parameters are clear.

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 leads with a specific verb+resource ('Federal court opinion search') and enumerates the retrieval modes ('keyword or party name search') and returned fields ('citation counts, court, date, and excerpt'). It is clear what the tool does, though it never distinguishes itself from adjacent federal-court siblings such as get_federal_court_cases or get_citation_authority.

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 / when-not-to-use guidance and no routing to an alternative tool. The only usage-adjacent content is 'Optional court filter (e.g. scotus, ca2, dcd)', which describes a parameter rather than the tool's role among the ~40 siblings.

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