Skip to main content
Glama

get_judge_analytics

Read-only

Federal judge profile — court positions, appointment history, political affiliation, education, and opinion count. Source: CourtListener (Free Law Project). Use when assessing litigation risk or evaluating judicial philosophy. 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": {
      "judge_name": "<judge_name>"
    },
    "name": "get_judge_analytics"
  }
}

Input Schema

NameRequiredDescriptionDefault
judge_nameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=true, so safety is covered; the description adds genuinely non-obvious behavior: the upstream source (CourtListener), a $0.50 USDC per-call cost, attestation via a signed receipt, and a verification URL. Cost and payment requirements are exactly the kind of operational context annotations cannot express. The attestation phrasing is marketing-flavored, but it does disclose a settlement/verification step an agent would otherwise not anticipate.

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 the resource and its contents, then usage, then provenance and cost — a sensible ordering with no filler sentences. The attestation/verification clause is the weakest link in density, but it encodes real operational facts rather than repetition.

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 one-parameter read tool with no output schema, the description adequately explains what comes back, where it comes from, and what it costs. It is incomplete on the one thing an agent must get right to call it successfully: how judge_name must be formed and what happens when the name is ambiguous, which neither the schema nor the description addresses.

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?

The single required parameter judge_name has 0% schema description coverage, so the description carries the full burden — yet it says nothing about expected format (full name vs. partial), whether matching is exact or fuzzy, or how ambiguous or zero-hit names are handled. For a name-keyed lookup that is a material gap the schema does not fill.

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 (a federal judge profile) and enumerates the concrete fields returned: court positions, appointment history, political affiliation, education, opinion count. No sibling in the supplied list covers judicial data, so differentiation is not a live concern, but the description also never names a verb form (retrieve/lookup) or states lookup semantics.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

'Use when assessing litigation risk or evaluating judicial philosophy' gives a clear situational trigger rather than leaving usage implicit. It stops short of exclusions (e.g., when a docket or opinion tool is the better fit) and names no alternative tool, so it is context without routing.

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