Skip to main content
Glama

Merge PDF

merge_pdf
Idempotent

Combine several PDFs into a single file, in the order you want, in a few seconds. Returns a link to download the result (kept about an hour). Credits on paid plans: 5 per file.

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": "merge_pdf"
  }
}

Input Schema

NameRequiredDescriptionDefault
filesYesInput files (.pdf), at least 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.2/5.0
Behavior4/5

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

Annotations already declare non-readOnly, non-destructive, idempotent, open-world behavior, so the description does not need to repeat safety. It adds real context beyond them: output is a download link valid for roughly an hour, processing takes a few seconds, and cost is 5 credits per file on paid plans — all material for deciding whether to call it and what to do next.

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?

Two short sentences, front-loaded with the operation, followed by the return value and cost. No filler, and every clause carries information an agent would otherwise have to guess.

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 single-parameter tool with a fully documented schema, the description covers purpose, output (link with ~1 hour retention), latency, and pricing. The only gap is failure behavior for oversized or invalid inputs, which is partly covered by the schema's 20 MB note.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline would be 3, but the description adds the ordering semantic ('in the order you want'), telling the agent that array position determines output page order — a detail the schema does not state. That is genuine meaning beyond the structured field.

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?

The description states a specific verb and resource ('Combine several PDFs into a single file') that is unmistakable and clearly distinct from sibling operations like split_pdf, compress_pdf, or compare_pdf. It also mentions order control, so an agent knows this is an ordered merge, not a bulk concatenation.

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?

Usage is implied by the verb 'combine' and by 'in the order you want', which hints that the input array order is preserved. However, there is no explicit when-to-use/when-not guidance and no reference to alternatives such as split_pdf for the reverse operation, leaving selection inference to the agent.

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