Skip to main content
Glama

TracePass DPP Compliance Assistant

Report a wrong or unclear answer

report_answer

Use it when the user says an answer was wrong or unclear. Pass their words and the ruleIds of the answer. The report goes to a review queue. Use only what this tool returns: add no facts, dates or articles of your own, not even today's date. Keep every citation and the disclaimer line, and any "Planned, not law yet" or "being re-checked" label. For inScope no, never say "not yet" or "yet"; for pending, name the planned act from data.planned. Phrase answers about the product type, never as personal duties ("you must"). Never rank or recommend vendors. Never call this advice or yourself a consultant. If the result is not_covered, say so and point to the article given.

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": {
      "what": "<what>"
    },
    "name": "report_answer"
  }
}

Input Schema

NameRequiredDescriptionDefault
whatYesThe user's own words describing what was wrong or unclear.
ruleIdsNoThe ruleIds from the answer that was reported. Pass them from the result unchanged.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already establish this is a non-destructive, non-idempotent write, so the description's added value is the destination: 'The report goes to a review queue.' That is genuinely useful. However, the rest of the description says 'Use only what this tool returns' and references result fields (inScope, pending, data.planned, not_covered), which suggests the tool returns substantive answer content, while the earlier sentence implies it merely files a report. This ambiguity is never resolved and leaves the agent unsure what actually comes back.

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

Conciseness2/5

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

The first two sentences are tight and front-loaded, but well over half the text is a policy block about how to phrase answers, vendor ranking, disclaimers, and label handling. None of that is about filing a report, and several sentences ('for inScope no', 'for pending', 'If the result is not_covered') reference terms introduced nowhere in this definition. The text reads as copied guidance from another tool and displaces what this tool's own behavior needs.

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 two-parameter write tool with no output schema, the essential behavioral fact (goes to a review queue) is present. But the description introduces output-field semantics that no output schema supports, without explaining whether report_answer actually returns them, and it never states what a successful report returns to the agent. The definition is partly complete but leaves the return contract unresolved.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%; both parameters are fully documented, including that ruleIds must be passed unchanged from the result. The description's 'Pass their words and the ruleIds of the answer' restates what the schema already states rather than adding syntax, sourcing, or edge-case detail. Baseline 3 applies.

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 opening sentence gives a specific verb and resource: file a report when a user says an answer was wrong or unclear. That is distinguishable from the sibling tools (scope_check, registry_guidance, what_changed). The purpose is muddied later by a long block of answer-phrasing policy that does not obviously belong to a reporting tool, but the core action is still identifiable.

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?

The trigger is explicit and concrete: 'Use it when the user says an answer was wrong or unclear.' It also says which inputs to pass. There are no explicit exclusions or named alternatives, but for a single-purpose reporting tool the context is unambiguous enough for an agent to select it.

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.