Skip to main content
Glama

audit_answer

Read-onlyIdempotent

Verify an answer's citations by checking each handle is genuine, its record still exists, and quotes match verbatim; flag forged, unavailable, retracted or uncited claims before publishing.

Instructions

Audit an answer's citations: genuine handle, record still exists, quotes verbatim.

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": "audit_answer"
  }
}

Input Schema

NameRequiredDescriptionDefault
claimsNo
fail_onNo
answer_textNoAnswer with [handle] citations

Output Schema

NameRequiredDescriptionDefault
claimsYes
fail_onYes
summaryYes
verdictYes
audited_atYes
contract_versionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

B3.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true, so safety and repeatability are covered structurally. The description earns credit beyond that by disclosing the actual checks performed: handle genuineness, record existence, and literal quote matching. It stops short of explaining what happens on failure or how fail_on alters behavior, but the check list is substantive behavioral context.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

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

A single compact sentence with the core purpose front-loaded and no filler. Every phrase (genuine handle, record exists, quotes verbatim) carries distinct meaning.

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

Completeness2/5

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

For a three-parameter tool with low schema coverage, the description leaves critical gaps: how claims and answer_text relate (both optional, potentially mutually exclusive), what fail_on does and which failure codes are available, and what the input forms are. The output schema exists, so return values need not be explained, but the input-side completeness is inadequate.

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 only 33%, with only answer_text documented as 'Answer with [handle] citations'. The description says nothing about the claims structure, the fail_on enum values (malformed, forged, unavailable, withdrawn, quote_mismatch, uncited, retracted), or whether claims and answer_text are alternatives. With low coverage, the description should compensate but does not.

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 verb and resource ('Audit an answer's citations') and enumerates the three checks: genuine handle, record existence, and verbatim quotes. It does not distinguish itself from the closer sibling resolve_handles, which likely also deals with handles, so sibling differentiation is absent.

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 explicit when-to-use or when-not-to-use guidance, no mention of alternatives such as resolve_handles or fetch_passages, and no prerequisites. The only guidance is implied by the verb 'audit', matching the calibration case that scored 2 for having no when-to-use or prerequisites.

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