Skip to main content
Glama

pdf_crop

Crop PDF pages to specific dimensions by defining a left, bottom, right, top box and saving the result to a new PDF file.

Instructions

Crops pages to specific dimensions. [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>",
      "box": "<box>",
      "output": "<output>"
    },
    "name": "pdf_crop"
  }
}

Input Schema

NameRequiredDescriptionDefault
boxYesThe crop box in format 'left,bottom,right,top' e.g. '0,0,595,842'.
inputYesThe input PDF file path.
outputYesFile path for the cropped output.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden and does not say whether the crop box applies to every page or a subset, what coordinate units are used, whether the operation is reversible, or what happens to out-of-range boxes. It discloses only that a new PDF file is written, which is already obvious from the required 'output' parameter.

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 sentences with the action front-loaded and format tags bracketed at the end; nothing is wasted. It could be slightly improved by folding the page-scope information into the first sentence rather than omitting it.

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?

For a simple three-parameter tool with a fully described schema and no output schema needed (the result is a file path), this is close to adequate. The notable gap is page scope: an agent cannot tell from the description whether the crop applies to all pages or a specific page, which materially affects how it would call the tool.

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 description coverage is 100%, so the box format, input path, and output path are all documented in the schema itself. The description adds no extra meaning such as default box values or unit conventions, so the baseline of 3 applies.

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 ('Crops pages') plus the input/output formats (PDF in, PDF out), which is enough to distinguish it from siblings like pdf_compress or pdf_extract_pages. It stops short of explicitly contrasting with any named alternative, so it lands at clear-but-undifferentiated.

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 about when to use this versus other PDF manipulation tools, no prerequisites, and no mention of alternatives. The only implied usage is that the input is a PDF and the output is a cropped PDF, which an agent could infer from the schema alone.

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