pdf-rescue-mcp

Overview Schema Source Related Servers Discussions Admin

查看页面证据

get_page_evidence

Retrieve OCR text, confidence scores, recognition blocks, and warnings for a specific page to verify recognition quality.

Instructions

读取指定页的识别文本、置信度、识别块和警告。

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": {
      "job_dir": "<job_dir>",
      "page_number": "<page_number>"
    },
    "name": "get_page_evidence"
  }
}

Input Schema

Name	Required	Description	Default
`job_dir`	Yes
`page_number`	Yes
`include_blocks`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 2, 2026

TDQS

B3.1/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full burden. It only states a read operation but does not disclose whether any side effects occur, what job state is required, or how errors are handled. There is no additional 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?

The description is a single concise sentence with no fluff. It is front-loaded and easy to scan.

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?

Although an output schema exists, the description is too minimal. It fails to provide the job context, parameter semantics, or any usage instructions, leaving the agent without enough information to invoke the tool correctly beyond basic name guessing.

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 has zero description coverage and the description does not explain the parameters. The meaning of include_blocks is especially ambiguous, as the description mentions '识别块' (recognition blocks) but does not link it to the optional parameter.

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?

The description clearly states the action ('读取'/'reads') and the specific resource (the specified page) and what data it retrieves (recognized text, confidence, blocks, warnings). This distinguishes it from sibling tools like export_page_image_evidence, which deals with images. The verb and object are specific.

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?

The description offers no guidance on when to use this tool versus alternatives or any context about prerequisites. It does not mention that it belongs to a job context or how it differs from inspection tools like inspect_pdf_text_layer.

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