Skip to main content
Glama

pdf-suite

pdf_compare

Structurally compare two PDFs (page count, page dimensions, metadata, SHA-256, and extracted text tokens) to pinpoint differences.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "pdf_compare"
  }
}

Input Schema

NameRequiredDescriptionDefault
base64DataNoFirst PDF base64.
secondBase64DataNoSecond PDF base64 (defaults to self-comparison if omitted).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden; it does disclose the comparison dimensions, which is real substance, and the read-only nature is implicit in "compare." However, it says nothing about the result shape or severity ranking, nothing about behavior on encrypted or unreadable PDFs, and nothing about size limits on the base64 payloads.

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?

A single front-loaded sentence with the verb and resource first and the compared attributes in a tight parenthetical. Every clause earns its place and there is no filler.

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?

There is no output schema and no annotations, so the description must stand in for both. The enumerated comparison dimensions serve as a rough proxy for what comes back, but the actual report structure, granularity of the diff, and error behavior are left unspecified for a tool whose whole value is its output.

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% and both parameters are documented there, including the self-comparison default, so the baseline is 3. The parenthetical list of compared attributes describes output content rather than parameter meaning, adding no syntax or format detail 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?

The description gives a specific verb plus resource ("Structurally compare two PDFs") and enumerates exactly what is compared: page count, dimensions, metadata, SHA-256, and extracted text tokens. No sibling tool in the supplied list performs comparison, so the role is unambiguous, though the description never explicitly distinguishes itself from the other pdf_* utilities.

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 stated prerequisites, and no mention of alternatives or exclusions. An agent must infer from the name alone that this is the tool for diffing two documents rather than, say, auditing or converting them.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources