Skip to main content
Glama

get_citation_authority

Read-only

Citation authority analysis — how many times a case has been cited, by which courts, and authority signal (landmark / highly cited / frequently cited / limited). 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

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_citation_authority"
  }
}

Input Schema

NameRequiredDescriptionDefault
citationNo
case_nameNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already cover safety (readOnly, non-destructive, openWorld), and the description adds genuinely useful context beyond them: the upstream source (CourtListener), a per-call price of $0.10 USDC, and cryptographic attestation with a verification URL. The cost disclosure in particular is material for tool selection and is not captured in any structured field. It stops short of 5 because nothing is said about rate limits, latency, or failure behavior for an external paid call.

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 is front-loaded in the first clause, which is good. However, roughly a third of the text is attestation/verification boilerplate ('post-quantum signed settlement receipt', verify URL) that is identical across the vendor's tools and contributes little to selecting or invoking this specific tool.

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 does a reasonable job of conveying what comes back (counts, courts, authority tier). Given only two simple string parameters and clear annotations, the main remaining hole is parameter usage guidance, which is notable but not fatal.

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% and both parameters (citation, case_name) are optional per the schema, yet the description says nothing about them — not which to supply, not whether one is preferred, not what happens if both or neither are given. For a lookup tool whose correctness hinges on identifier choice, this is a real gap the description should have filled.

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 names a specific resource (citation authority) and enumerates the concrete outputs: citation count, citing courts, and an authority signal with named tiers (landmark / highly cited / frequently cited / limited). This is clearly distinguishable from synthesis-oriented siblings such as get_case_law_synthesis. It falls short of a 5 only because it is framed as a noun phrase ('Citation authority analysis') rather than stating a direct action.

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 the enumerated outputs — an agent can infer this is the tool for citation-count/authority questions — but there is no explicit when-to-use, when-not-to-use, or named alternative. No prerequisites or exclusions are stated.

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