Skip to main content
Glama
Federal Courts Analyst

Federal Courts Analyst

Save a verified answer (sandbox)

save_verified_answer
Idempotent

Validate an answer's figures against cited official values and server read-tool results; save it to the request only after checks pass and the user confirms. Returns issues if checks fail.

Instructions

Use this after open_request, when the user wants the answer kept: it checks the answer and saves it to the request only if it passes. The check: every number in the text is a cited official value, a number the server's read tools produce (pass the calls the answer relied on in tool_calls; the server re-runs them), a published threshold such as 430, or a difference or percentage of backed numbers; each citation matches what its edition printed; and one measure's figures come from consistent editions. An earlier edition's value may be quoted as history in a sentence that says so ("first published as 554").

Not for creating the request (use open_request) or for asking why a figure changed (use file_revision_inquiry after saving).

Returns whether it was saved and, if not, each problem with the number and what to write instead. Writes only after the user confirms.

Example: text='322 in FY2020 and 318 in FY2021 (JFF-2024)', citations for both → saved; quoting 554 (JB-2020) beside 318 (JFF-2024) → refused, mixed editions.

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": {
      "request_id": "<request_id>",
      "text": "<text>",
      "citations": "<citations>"
    },
    "name": "save_verified_answer"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesThe answer.
confirmNoTrue once the user has agreed to this write. False (default) asks the user, or returns a preview if the client can't ask.
citationsYesOne entry per official figure the answer quotes, with the edition it was quoted from.
asker_nameNoA display name for the asker (demo identity; the same name must be used for every call about one request).MCP user
request_idYesFrom open_request.
tool_callsNoThe read tools the answer relied on (name and arguments, e.g. explain_change with its arguments). The server re-runs them; numbers their outputs hold count as backed. Never send values.
idempotency_keyNoAny unique string; a retried call with the same key returns the first result instead of writing again.

Output Schema

NameRequiredDescriptionDefault
dataNo
statusNook
declinedNo
warningsNo
provenanceNo
clarificationNo
suggested_nextNoHints for a follow-up call.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare the write and idempotency profile (readOnlyHint=false, idempotentHint=true), and the description goes well beyond them by spelling out the confirmation gate ('Writes only after the user confirms') and the full validation contract that determines whether the write lands. The only gap is that it does not restate retry or rate-limit behavior, though the idempotency key in the schema covers retries.

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 trigger and the exclusions, and every clause carries real information about a nontrivial validation rule; the worked example of an accepted and a refused answer earns its space. The dense middle paragraph mixes several rules into one sentence and could be broken into a list, which keeps it from a 5.

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?

For a complex 7-parameter mutation tool, the description covers the trigger, ordering, exclusions, confirmation gate, the full pass/fail rule set, and error content, and an output schema exists so return values need no further explanation. The historical-quote exception is explicitly covered, leaving no obvious gap for a caller.

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%, so the baseline is 3; the description earns above that by explaining the semantics of citations and tool_calls in the validation process (the server re-runs the listed calls, and their numeric outputs count as backed), which the schema alone does not convey. The concrete example of numeric forms (threshold like 430, differences, percentages) further clarifies what values are acceptable.

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?

States a specific verb and resource (save a verified answer), plus the conditional nature of the write (validated first, saved only if it passes). It explicitly contrasts itself with open_request and file_revision_inquiry, so an agent can distinguish it from siblings without opening any schema.

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

Usage Guidelines5/5

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

Gives an explicit trigger and ordering ('Use this after open_request, when the user wants the answer kept') and two explicit exclusions with named alternatives (open_request for creating the request, file_revision_inquiry for why a figure changed). Nothing about when to call it is left to inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.