Skip to main content
Glama

pdf-suite

pdf_remove_pages

Delete specified 1-based page numbers or ranges from a PDF document.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "pdf_remove_pages"
  }
}

Input Schema

NameRequiredDescriptionDefault
inputPathNo
base64DataNo
outputPathNo
removePagesNoPages to delete e.g. "2,4-5".

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 are supplied, so the description carries the full burden, yet it only states that pages are deleted. It does not say whether the source file is modified or a new file is written, what role outputPath plays, whether inputPath and base64Data are alternatives, or how out-of-range page numbers are handled.

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?

A single tight sentence with the key scope detail front-loaded and no wasted words. Its brevity is a virtue structurally, even though the content is thin elsewhere.

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 4-parameter mutation tool with no annotations, no output schema, and 25% schema coverage, one sentence is not enough. An agent cannot determine input mode selection, output destination, or failure behavior from this definition.

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 25%: only removePages is documented (schema already gives the "2,4-5" example, so the description adds little beyond the 1-based note). The three I/O parameters (inputPath, base64Data, outputPath) get no explanation of their mutual exclusivity or destination behavior, which the low coverage requires.

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?

Names a specific verb (delete) and resource (page numbers or ranges in a PDF), and adds the 1-based indexing detail that disambiguates the page addressing convention. It does not explicitly contrast with sibling pdf_extract_pages (keep a subset vs. remove a subset), so differentiation is left to inference.

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?

No when-to-use or when-not-to-use guidance: nothing says to prefer pdf_extract_pages when the goal is keeping a subset, nor when to choose pdf_split instead. The description gives no preconditions (e.g., encrypted documents, invalid ranges) or expectations about output.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources