Skip to main content
Glama

Compare two documents

compare_pdf
Idempotent

Upload two versions of a contract, report or tender, as PDF or Word, and we mark what was added and what was removed. Returns a link to download the result (kept about an hour). Credits on paid plans: 2 per page.

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": {
      "files": "<files>"
    },
    "name": "compare_pdf"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoLanguage. Language of the texts the tool adds. Values: 'es' = Spanish; 'en' = Englishes
filesYesInput files (.pdf, .doc, .docx, .odt, .rtf), exactly 2. Each one is a public http(s) URL, or an object with `url`, or with `name` and `content_base64` (small files only: up to 20 MB in total).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Goes beyond the annotations (readOnlyHint=false, openWorldHint=true, idempotentHint=true) by disclosing the return artifact (a download link), its short retention window (~1 hour), and the credit cost of 2 per page. It does not explain how URLs are fetched or what happens if a document fails to parse, but the operational essentials are covered.

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?

Three short sentences, front-loaded with the action and input, followed by output and cost. Every sentence carries distinct information with no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter tool with full schema coverage, annotations, and no output schema, the description covers input, output, retention, and pricing. The only gap is that it advertises fewer formats than the schema allows, slightly underselling accepted input.

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%, so the schema already documents `files` (exactly 2, URL or base64, 20 MB cap) and `lang`. The description only echoes that PDF or Word is accepted, which actually understates the schema's list (.odt, .rtf) and adds no new parameter meaning.

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

Purpose5/5

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

States a concrete verb and resource — upload two versions of a document and get a marked-up diff of additions and removals — and names the document types it handles. It is immediately distinguishable from siblings like merge_pdf or split_pdf, which manipulate pages rather than compare versions.

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 description implies when to use it (comparing two versions) and constrains input to exactly two files, but it never states when *not* to use it or names an alternative path among the many PDF siblings. Usage is inferable rather than explicit.

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