Skip to main content
Glama

pdf_scale_pages

Resize PDF pages to standard formats or percentage scales to fit print or layout needs, producing a new PDF with adjusted dimensions.

Instructions

Scale Page Dimensions: Scale page dimensions between standard formats or percentages. [Input: .pdf | Output: .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_scale_pages"
  }
}

Input Schema

NameRequiredDescriptionDefault
inputYes
outputYes

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?

No annotations are supplied, so the description carries the full behavioral burden. It only says the input and output are both .pdf; it does not disclose whether scaling rasterizes content, flattens the text layer, preserves annotations or form fields, 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, front-loaded fragments with no filler, and the input/output format notation is easy to scan. It is arguably too terse, leaving the mechanism unspecified, but nothing is wasted.

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 file mutation tool with no annotations and no output schema, the definition is thin: no description of where the scale value comes from, no side-effect disclosure, and no mention of formatting side effects. An agent could not confidently call this correctly.

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 coverage is 0% for the two parameters, so the description should compensate. It indicates both input and output are .pdf, which is mildly useful, but it never explains how the scale target is specified, despite there being no scale parameter visible in the schema.

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 ('Scale page dimensions') and clarifies the operation as resizing between standard formats or percentages. That distinguishes it reasonably from siblings like pdf_crop or pdf_compress, though no sibling is named explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The phrase 'between standard formats or percentages' implies the two scaling modes, which gives some hint of when to use it. However, there is no explicit guidance on when to prefer this over pdf_crop or pdf_compress, and no prerequisites or exclusions are stated.

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