Skip to main content
Glama

pdf_linearize

Optimizes a PDF for fast web view by rearranging it for progressive download, then saves the result to a new PDF file.

Instructions

Linearizes a PDF for fast web view. [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_linearize"
  }
}

Input Schema

NameRequiredDescriptionDefault
inputYesPath to the PDF to linearize.
outputYesPath to save the linearized PDF.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden, and it discloses almost nothing behavioral beyond the one-line purpose. It does not say whether linearization is lossless, how file size changes, what happens with encrypted or malformed PDFs, or whether the output path is overwritten. The input/output format tag is the only added context.

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 compact sentences with the purpose front-loaded and a consistent input/output convention that lets an agent confirm the data type at a glance. Nothing is padded, though the bracket notation repeats what the schema already states.

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 two-parameter conversion tool with a fully documented schema and no output schema, the essentials are present. However, with zero annotations the description should at least note mutation/overwrite behavior and edge cases like encrypted inputs, which it omits.

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 coverage is 100% with both parameters self-documented ('Path to the PDF to linearize', 'Path to save the linearized PDF'), so the baseline is 3. The description adds no format, path-resolution, or overwrite semantics beyond 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?

Names a specific verb and resource ('Linearizes a PDF') and adds the goal ('for fast web view'), so the operation is unmistakable. It does not explicitly distinguish itself from siblings, but none of the listed siblings share this purpose, so disambiguation is largely unnecessary.

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 'for fast web view' implies the scenario (publishing/large documents served over the web), but there is no explicit when-to-use, when-not-to-use, or prerequisite guidance. An agent must infer the trigger condition from the purpose phrase alone.

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