Skip to main content
Glama

pdf_dedup_streams

Remove duplicate indirect object streams from PDFs with lossless hash matching and compress images safely for CMYK workflows to shrink files without color shifts.

Instructions

Lossless Stream Deduplication: Lossless hash-based indirect object stream deduplication & CMYK-safe image compression [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_dedup_streams"
  }
}

Input Schema

NameRequiredDescriptionDefault
inputYes
outputYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.7/5.0
Behavior2/5

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

No annotations exist, so the description carries the full behavioral burden. It does disclose the useful traits 'lossless' and 'CMYK-safe', but says nothing about whether the output path may overwrite an existing file, whether the input is modified, whether the operation is CPU- or time-intensive, or what happens on hash collisions or unsupported PDF versions.

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?

A single compact line with the operation front-loaded and the input/output contract bracketed at the end — no filler. The density of jargon ('hash-based indirect object stream deduplication') borders on opaque, 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-in/file-out transform with no annotations and no output schema, the definition should at minimum state the overwrite contract and how it differs from pdf_compress. It supplies neither, leaving an agent unable to call it safely on an existing output file.

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% for both required parameters, so the description must compensate. '[Input: .pdf | Output: .pdf]' adds file-format meaning beyond the bare string type, but there is no explanation of path semantics, whether output may equal input, or overwrite behavior — the critical ambiguity for file-writing parameters.

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 states a specific operation — hash-based indirect object stream deduplication plus CMYK-safe image compression — on a specific resource (PDF streams). It is more concrete than a generic 'compress' label, but it never names the obvious sibling pdf_compress, so an agent cannot tell the two apart from the text alone.

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?

No when-to-use guidance is given: no statement of when deduplication is preferable to plain pdf_compress, no prerequisites, and no exclusions. The only usage signal is the implicit 'lossless' property and the bracketed .pdf-to-.pdf format.

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