Skip to main content
Glama

pdf_compress

Compress PDF files to reduce their size while preserving content, with adjustable quality presets or a 1–100 setting.

Instructions

Compresses a PDF to reduce file size. [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_compress"
  }
}

Input Schema

NameRequiredDescriptionDefault
inputYesThe input PDF file path.
outputYesThe output PDF file path.
qualityNoCompression quality preset (low, medium, high) or integer 1-100

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations, the description carries full behavioral burden, yet it only states the input and output formats. It says nothing about whether compression is lossy, whether the text layer or embedded images survive, whether the original file is modified, memory/size limits, or whether permissions/encryption affect it.

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?

Two compact sentences, purpose front-loaded, with the format note kept to a parenthetical tag. Nothing is padded or redundant beyond a minor restatement of what the schema already types.

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 documented schema and no output schema, the definition covers what the tool does and its I/O types. It is still thin on the behavioral side — quality tradeoffs and fidelity implications are unaddressed, which matters for a lossy-sounding operation.

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 input, output, and quality parameters are already documented with types and the quality preset values (low, medium, high) or 1-100 integer. The description adds no meaning beyond the schema, so the baseline 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?

"Compresses a PDF to reduce file size" gives a specific verb (compress) and resource (PDF) plus the intent (size reduction), which is enough to distinguish it from the surrounding conversion/annotation/extraction siblings. It does not explicitly name a sibling or contrast itself with alternatives, so it stops short of 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?

There is no guidance on when to choose compression versus other operations, no mention of prerequisites, and no advice on when compression is inappropriate (e.g., when a text layer or image fidelity must be preserved). The agent is left to infer usage entirely from the name.

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