pdf-rescue-mcp

Overview Schema Source Related Servers Discussions Admin

后台提取书籍

extract_book_background

Starts a resumable background OCR extraction for an entire book, returning task ID and process info immediately. Ideal for scanning long PDFs without blocking.

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": {
      "path": "<path>"
    },
    "name": "extract_book_background"
  }
}

Input Schema

Name	Required	Default
`mode`	No	book-balanced
`path`	Yes
`resume`	No
`max_pages`	No
`output_dir`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 2, 2026

TDQS

A3.6/5.0

Behavior3/5

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

No annotations are provided, so the description carries full burden. It discloses key behaviors: resumable, asynchronous (immediate return), and background execution. However, it omits details on monitoring, cancellation, or failure modes, which are relevant for a background task.

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?

Single sentence that front-loads the action and includes key context (resumable, immediate return, suitability for long scans). No redundant or filler content.

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 description covers the core purpose and basic behavior, but with 5 parameters and no parameter explanations, it is not fully complete for an agent to invoke correctly. The existence of an output schema reduces the need to describe return values, yet the lack of parameter semantics and monitoring guidance leaves gaps.

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

Parameters1/5

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

Schema description coverage is 0%, and the description does not mention any of the 5 parameters (path, mode, resume, max_pages, output_dir). It fails to compensate for the complete lack of parameter documentation, leaving the agent without guidance on how to fill the schema fields.

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 'start a resumable whole-book background extraction task' with immediate return of task catalog and process info. This specific verb+resource+mode distinguishes it from siblings like extract_book_text (foreground) and batch_extract_library (batch).

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?

Explicitly notes it is 'suitable for long-time scanning books', providing a clear when-to-use context. Does not name alternatives or exclusions, but the background/resumable nature implies a contrast with synchronous or short-run tools.

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