Skip to main content
Glama

pdf-suite

pdf_crop_margins

Trim uniform PDF CropBox margins (in points) across all pages while preserving vector content.

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_crop_margins"
  }
}

Input Schema

NameRequiredDescriptionDefault
marginPtNo
inputPathNo
base64DataNo
outputPathNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.8/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. It usefully discloses that vector content is preserved and that the change spans all pages, but it is silent on whether the source file is modified in place or a new file is written, what happens with non-uniform margins, and whether the operation is reversible. For a mutation tool with zero annotation coverage this is a substantial gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with no filler; the verb and resource lead, and the qualifier about vector content is appended rather than buried. Every clause carries information.

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 mutation tool with four parameters, no annotations, no output schema, and 0% schema coverage, the definition is too thin: input source selection, output destination, return value, and in-place versus copy semantics are all unresolved. The description only covers the crop semantics.

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%, so the description must explain the four parameters. It only clarifies marginPt as being in points; the relationship between inputPath, base64Data, and outputPath (which are the only way to supply and receive the file, and with zero required parameters, how input is selected) is left entirely undocumented.

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?

States a specific verb and resource: 'Trim uniform PDF CropBox margins ... across all pages.' It also discloses a key side-effect ('preserving vector content'), which distinguishes it from rasterizing compressors like pdf_compress. It stops short of naming a sibling or contrasting it, so a 4 rather than a 5.

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?

The word 'uniform' implies a precondition (only equal margins on every page), but the description never states when to choose this over pdf_compress or pdf_rotate, nor what to do when margins are not uniform. There are no explicit exclusions or alternative-routing guidance, leaving usage entirely to inference.

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