Skip to main content
Glama

pdf_compare

Compare two PDF files and generate a JSON report to identify differences between them.

Instructions

Compares two PDFs. [Input: 2 PDFs | Output: JSON report (.json)]

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_a": "<input_a>",
      "input_b": "<input_b>"
    },
    "name": "pdf_compare"
  }
}

Input Schema

NameRequiredDescriptionDefault
file1No
file2No
file_aNo
file_bNo
outputNoThe output diff file path.
input_aYesFirst input PDF file path.
input_bYesSecond input PDF file path.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.6/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 does disclose the input count and output format (JSON report), which is useful, but leaves out what comparison semantics are used, whether encrypted or malformed PDFs are handled, and how differences are reported. For a 7-parameter 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.

Conciseness4/5

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

Two compact segments with the input/output contract front-loaded in a bracketed form. Nothing is wasted, though the extreme terseness is what leaves the alias ambiguity unresolved.

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?

An output format is stated, which compensates for the absent output schema. But with 7 parameters, three overlapping input naming schemes, and no annotations, the definition does not give an agent enough to invoke the tool confidently without guessing which parameters to populate.

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 only 43%, and the schema exposes three parallel pairs of input parameters (file1/file2, file_a/file_b, input_a/input_b) that appear to be aliases. The description says only "2 PDFs" and does not clarify which pair to use, whether the others are deprecated, or that an output path can be supplied. This ambiguity is the most consequential gap in the definition.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ("Compares two PDFs"), so the basic operation is identifiable. However, it says nothing about what dimension of comparison is performed (text, layout, images, metadata), and no sibling is named to delineate it from the many other pdf_* utilities. It is clear but thin.

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 when-to-use guidance, no preconditions, and no mention of an alternative tool for any adjacent task. The agent must infer entirely from the name when comparison is the right operation.

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