Skip to main content
Glama

A numbered AlphaCitation ruling on an evidence conflict

lookup_precedent_ruling
Read-onlyIdempotent

For one ruling identifier (ACPREC-YYYY-NNNN): what was decided about an evidence conflict, why, on which records, its status now (settled, unresolved or superseded) and its RFC 3161 timestamp where one has been issued, together with a fresh lookup of the current governing record for the ruling's medicine, market and date where the ruling names one. A ruling is not evidence and decides no claim today; the current governing record does, and the ruling records only how the earlier conflict was decided. Where no current record is held, the answer names the competent authority and where its own record is published.

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": {
      "id": "<id>"
    },
    "name": "lookup_precedent_ruling"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe ruling identifier, for example ACPREC-2026-0001.
dateNoThe date to resolve the current record for, YYYY-MM-DD. Defaults to today (UTC).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

The description carries the full burden of disclosure beyond the annotations (which only state readOnly/idempotent/closed-world) and adds real value: the ruling's status vocabulary (settled, unresolved, superseded), the existence of an RFC 3161 timestamp where issued, and the fallback behavior when no current record is held (it names the competent authority and where its record is published). What it does not state is whether the response also fails or degrades gracefully, or how the fresh lookup is performed.

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 identifier format and the returned facts, and the remaining two sentences earn their place by disambiguating the ruling from live evidence. It is dense and slightly run-on, particularly the first sentence, which packs five output facts into one clause chain.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema exists, so the description must describe return values, and it does so completely: decision, rationale, source records, status, timestamp, the fresh governing-record lookup, and the no-record fallback. For a two-parameter read-only lookup this leaves nothing an agent would need missing.

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 coverage is 100%, but the description adds meaning beyond the schema: it establishes that the date parameter drives resolution of the current governing record against the ruling's medicine, market and date, not just a generic lookup date. That clarifies the purpose of the otherwise ambiguous optional parameter.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Names a specific verb and resource ('For one ruling identifier ... what was decided about an evidence conflict') and enumerates the exact payload: decision, rationale, records, status, RFC 3161 timestamp, plus a fresh lookup of the current governing record. It also draws a sharp semantic boundary ('A ruling is not evidence and decides no claim today'), which separates it from lookup_medicine_evidence even without naming it.

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?

Gives clear usage context: consult this for how an earlier conflict was decided, and do not treat the ruling as evidence for a claim today. What is missing is explicit routing (e.g. 'for current evidence use lookup_medicine_evidence'); the alternative is only implied by the 'current governing record does' sentence.

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.