Skip to main content
Glama

pdf_remove_blank

Remove blank pages from a PDF to clean up scanned or compiled documents. Output a PDF containing only content pages.

Instructions

Removes blank pages from a PDF. [Input: PDF (.pdf) | Output: 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": {
      "input": "<input>",
      "output": "<output>"
    },
    "name": "pdf_remove_blank"
  }
}

Input Schema

NameRequiredDescriptionDefault
inputYes
outputYes
sensitivityNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.7/5.0
Behavior2/5

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

No annotations exist, so the description carries the full behavioral burden, and it discloses only that the input and output are PDFs. It does not state whether the source file is overwritten or a new file is written, how 'blank' is detected (and whether that is tunable), or whether the operation is reversible.

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?

Two short clauses, front-loaded with the action and followed by the compact I/O format tag; nothing is wasted. The tradeoff is that terseness here reflects under-specification rather than disciplined editing.

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?

For a three-parameter mutation tool with no annotations, no output schema, and zero schema description coverage, the definition is too thin. An agent knows what the tool does in general terms but lacks the parameter meaning and behavioral detail needed to invoke it confidently.

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% for three parameters, and the description only implicitly maps 'input' and 'output' to PDF file paths via the bracket notation. The 'sensitivity' parameter—likely the blank-detection threshold—is left entirely unexplained in both schema and description, which is the most consequential gap.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a specific verb and resource: 'Removes blank pages from a PDF,' which is unambiguous about what the tool does. It does not explicitly contrast with the closely related sibling pdf_delete_pages, so the agent must infer that this targets only blank pages, but the core purpose is clear.

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?

There is no guidance on when to use this versus alternatives such as pdf_delete_pages (page-level deletion) or pdf_dedup_streams. No prerequisites, no exclusions, and no indication of when the tool might be inappropriate are provided.

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