pdf-rescue-mcp

Overview Schema Source Related Servers Discussions Admin

导出页面图像证据

export_page_image_evidence

Render a specified PDF page to an image for audit evidence, saving it to an audit directory. Supports password-protected PDFs and returns the image path, page record, and source PDF information.

Instructions

把指定页渲染成图片，保存到审计目录，并返回图像路径、页面记录和来源PDF；支持密码保护PDF。

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

Input Schema

Name	Required	Description	Default
`dpi`	No
`job_dir`	Yes
`password`	No
`page_number`	Yes

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 2, 2026

TDQS

B3.4/5.0

Behavior3/5

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

With no annotations provided, the description carries full responsibility. It discloses that the tool writes an image to the audit directory and can handle password-protected PDFs, which is useful side-effect information. However, it omits other behavioral traits such as whether the original PDF is modified, overwrite behavior, or required permissions.

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 compact sentence that front-loads the primary action (render/save/return) and adds the password feature. There is no redundant information.

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?

The tool has an output schema, so return values are covered, and the description lists the key outputs. However, it lacks context about when to use this tool and does not clarify the role of job_dir or dpi, making it only partially complete for an agent.

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%, so the description must compensate. It implicitly maps 'specified page' to page_number and 'password-protected PDF' to password, but does not explain dpi or job_dir. Thus, it adds some meaning but leaves half the parameters undocumented.

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 tool's function: rendering a specified page to an image, saving it to the audit directory, and returning image path, page record, and source PDF. This specific verb-resource combination distinguishes it from sibling tools like get_page_evidence.

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 provides no guidance on when to use this tool versus alternatives like get_page_evidence or diagnose_pdf. It does not mention any context, prerequisites, or exclusions.

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