Skip to main content
Glama

pdf_merge_alternate

Merge two PDF documents by interleaving their pages alternately into one output file, with optional step sizes and page-order reversal.

Instructions

Alternating PDF Merge: Interleave pages from two PDF documents. [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_a": "<input_a>",
      "input_b": "<input_b>",
      "output": "<output>"
    },
    "name": "pdf_merge_alternate"
  }
}

Input Schema

NameRequiredDescriptionDefault
stepNo
outputYes
step_bNo
input_aYes
input_bYes
reverse_aNo
reverse_bNo

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?

With no annotations, the description carries the full burden, and it only adds the input/output file types. It says nothing about what happens when the two inputs have unequal page counts, whether extra pages are appended or dropped, or any auth/overwrite behavior for the output file.

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?

The definition is a single tight sentence with the operation front-loaded and the format tags bracketed at the end. Very little waste, though the format tags are the only added value in the second half.

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 7-parameter tool with no annotations, no output schema, and zero schema description coverage, the definition is far too thin. An agent cannot determine the meaning of the step, step_b, or reverse_* parameters from anything supplied.

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% across 7 parameters, so the description must compensate and largely fails. It implies the two inputs are PDFs, but step, step_b, reverse_a, reverse_b, and output naming are entirely undocumented.

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 names a specific operation (interleaving pages from two PDF documents) with a clear verb+resource, which distinguishes it from a plain merge. It does not explicitly name the pdf_merge sibling, but 'Alternating' versus ordinary merge is inferable.

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 guidance on when to choose this over pdf_merge or other merge-like siblings, and no prerequisites or exclusions are stated. The agent must infer the use case entirely from the word 'Alternating'.

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