Paperboy

Official

Overview Schema Source Related Servers Discussions Admin

find_blank_pages

Read-onlyIdempotent

Locate blank and nearly blank pages in PDFs, separate truly empty pages from those with faint marks, and review risky pages before deleting them.

Instructions

Find blank pages (no text, no ink) and nearly blank ones (no text, a little ink).

blank_pages can be passed to delete_pages. nearly_blank_pages may hold scanner dust but also a stamp, initials or faint pencil: look at them with view_pages before deleting. ink_threshold_percent (0-5, default 0.005) is how much of a page may differ from its background and still be blank. If complete is false, the time limit stopped the scan after pages_checked pages; call again for the rest.

Any password argument can be "ask": the user then types it on a local page, so it never passes through the chat.

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": {
      "input_path": "<input_path>"
    },
    "name": "find_blank_pages"
  }
}

Input Schema

Name	Required	Description	Default
`pages`	No
`password`	No
`input_path`	Yes
`ink_threshold_percent`	No

Output Schema

Name	Required	Description	Default
`path`	Yes
`details`	Yes
`complete`	Yes
`blank_pages`	Yes
`total_pages`	Yes
`pages_checked`	Yes
`nearly_blank_pages`	Yes
`ink_threshold_percent`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Addedv0.1.1Nov 12, 2026

TDQS

A4.3/5.0

Behavior5/5

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

Goes well beyond the readOnly/idempotent annotations: it explains the pagination/truncation contract (complete=false with pages_checked means the time limit cut the scan off and you must call again), documents the ink_threshold_percent range and default, and reveals the 'ask' password mode that keeps secrets out of the chat transcript.

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?

Front-loaded with the core purpose, then result semantics, then thresholds, then the truncation caveat, then the password note. Every line is useful, though the trailing password sentence is generic boilerplate rather than tool-specific.

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?

An output schema exists, yet the description still helpfully names the returned fields (blank_pages, nearly_blank_pages, complete, pages_checked) and explains what to do with them. The remaining gap is the undocumented 'pages' and 'input_path' parameters for a read-only tool with low schema coverage.

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 coverage is 0%, so the description carries the full burden. It meaningfully explains ink_threshold_percent (0-5, default 0.005, proportion of page allowed to differ from background) and the special 'ask' value for password, but never mentions what the 'pages' parameter accepts or what input_path expects, leaving 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?

States a specific verb and resource ('Find blank pages') and immediately defines both result classes: blank (no text, no ink) and nearly blank (no text, a little ink). An agent can distinguish this from siblings like check_pdf or view_pages without opening any schema.

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?

Gives clear downstream routing: blank_pages can be fed to delete_pages, while nearly_blank_pages must be inspected with view_pages first because they may contain stamps, initials or faint pencil. It lacks an explicit 'don't use this when...' exclusion, but the workflow guidance is concrete and actionable.

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