docbridge

Overview Schema Source Related Servers Discussions Admin

get_report

Read-onlyIdempotent

Retrieve the full validation report or a specific section (axes, structure checks, differences, warnings, unsupported checks) for a report_id from the last 200 server operations.

Instructions

The full validation report behind a report_id (held for the last 200 operations of this server session), or one section of it: axes, structure_checks, differences, warnings, unsupported_checks. [docbridge schema 0.2.4]

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": {
      "report_id": "<report_id>"
    },
    "name": "get_report"
  }
}

Input Schema

Name	Required	Description	Default
`section`	No		all
`report_id`	Yes

Output Schema

Name	Required	Description	Default
`tool`	Yes
`error`	No
`report`	No
`section`	No
`report_id`	No
`schema_version`	Yes
`operation_completed`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.4Sep 28, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and openWorld=false, so the safety profile is covered. The description adds a genuinely useful non-annotated trait: the report is only retained for the last 200 operations of the session, warning the agent of expiry. It omits error behavior when a report_id is stale.

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?

A single front-loaded sentence with the core purpose first, then section options, then the retention caveat. The trailing schema-version tag is minor noise but the whole is tight.

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

Completeness4/5

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

With an output schema present, return values need no explanation, and the description covers purpose, section selection, and retention. The one gap is not stating which operation produces the report_id, leaving provenance implicit.

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 description coverage is 0%, so the description must carry the burden. It lists the section values (axes, structure_checks, differences, warnings, unsupported_checks), helping map the enum, but does not explain what each section contains and adds nothing about the report_id format.

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 resource (the validation report behind a report_id) and explicitly frames the choice between the full report and one section. A verb is only implied ("get"), and no sibling tool is named, so it stops short of full sibling differentiation.

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

Usage Guidelines3/5

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

Usage is only implied: the agent is expected to already hold a report_id from a prior validation. The retention note (last 200 operations) hints at when a report is still retrievable, but no explicit when-to-use, exclusions, or alternatives are offered.

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

Deploy Server