VERDICT

Overview Schema Source Related Servers Discussions Admin

report_build

Build a structured investigative narrative and accuracy report from the ledger and provenance. Optionally score findings against a ground truth YAML answer key.

Instructions

Build the structured investigative narrative and the accuracy report from the ledger and provenance. If ground_truth_path is given (a YAML answer key), the accuracy report scores findings against it.

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

Input Schema

Name	Required	Description	Default
`case_name`	No
`ground_truth_path`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jun 14, 2026

TDQS

A3.6/5.0

Behavior2/5

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

No annotations are provided, and the description does not disclose side effects (e.g., overwriting existing reports), required permissions, or whether the operation is reversible. The description only states what the tool does, not its behavioral implications.

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?

Two sentences, no wasted words, front-loaded with the verb 'Build'. Efficiently communicates the core purpose and optional behavior.

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?

Given the tool's low complexity (2 optional params) and the presence of an output schema, completeness is moderate. However, lack of usage context and behavioral details reduces completeness.

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%. The description adds meaning only for ground_truth_path (a YAML answer key) but does not explain the case_name parameter. This partial coverage leaves a significant gap.

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?

Description clearly states it builds a structured investigative narrative and accuracy report from ledger and provenance, distinguishing it from sibling tools that focus on other tasks like auditing, file system operations, or memory analysis.

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?

Implies when to use the ground_truth_path parameter but does not explicitly state when this tool should be used versus alternatives. However, it is the only tool for building reports, so guidance is adequate.

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