pdf-rescue-mcp

Overview Schema Source Related Servers Discussions Admin

安全停止任务

cancel_job

Stop a running book processing job at the current page boundary. The cancellation request persists even if OCR becomes unresponsive, ensuring the MCP server is not blocked.

Instructions

请求正在运行的书籍任务在当前页边界安全停止。请求会持久化；OCR 无响应时监管层会按跨平台进程树策略清理，MCP 不会被阻塞。

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>"
    },
    "name": "cancel_job"
  }
}

Input Schema

Name	Required	Description	Default
`reason`	No		用户请求停止
`job_dir`	Yes

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 2, 2026

TDQS

A3.8/5.0

Behavior5/5

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

With no annotations, the description fully carries the burden and excels: it reveals that the stop request is persisted, occurs at page boundaries, triggers a cross-platform process-tree cleanup if OCR becomes unresponsive, and guarantees the MCP will not be blocked. These are substantial behavioral details beyond a simple cancel operation.

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?

The description is two sentences, with the core action front-loaded in the first sentence. The second sentence adds valuable technical context about persistence and cleanup, though it is dense; overall, it is efficient and earns its length.

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?

The description covers graceful stopping, persistence, fallback cleanup, and non-blocking behavior, and an output schema exists so return values need not be described. However, it omits edge cases like idempotency or resumability (relevant given sibling resume_job) and does not state prerequisites such as job_dir validity, leaving minor 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 coverage is 0% and the description provides no explanation of the required 'job_dir' or optional 'reason' parameters. The description mentions '请求' and '用户请求' but fails to map these to the schema, leaving the agent without any guidance on parameter meanings or formats.

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 uses a specific verb '安全停止' and targets a clear resource, '正在运行的书籍任务', with a precise scope, '当前页边界'. This distinguishes it from sibling tools like stop_batch, which stops batches rather than individual jobs, making the purpose unambiguous.

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?

The description implies the tool is for stopping a running book task, but it does not explicitly state when to prefer this over alternatives like stop_batch or resume_job, nor does it provide exclusions or conditions. Usage context is only implied, not clearly articulated.

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