Skip to main content
Glama

pdf-suite

pdf_merge

Merge multiple base64-encoded PDF documents cleanly in exact page order via pdf-lib.

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_merge"
  }
}

Input Schema

NameRequiredDescriptionDefault
base64DataNoPrimary PDF base64 (used if documentsBase64 omitted).
outputPathNo
documentsBase64NoArray of base64 PDFs to concatenate.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/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 behavioral burden and falls short. It does add useful facts (inputs are base64, page order is preserved, pdf-lib is the engine), but it never says what the tool returns versus what outputPath does, whether a file is written to disk, or what limits/errors exist on large inputs.

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?

One front-loaded sentence with no padding; 'cleanly' and the pdf-lib reference are the only marginally expendable tokens. Nothing important is buried.

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 merge tool with no annotations, no output schema, and an undocumented outputPath parameter, the definition is too thin. An agent cannot tell from it whether the merged PDF comes back as a base64 string or lands at outputPath, which is the key decision before calling.

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 coverage is 67%, and the uncovered parameter is outputPath, which the description also ignores. The description adds no meaning beyond the schema's own note that base64Data is used when documentsBase64 is omitted, leaving the disk-write vs. return-value question unresolved.

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 verb and resource ('Merge multiple base64-encoded PDF documents') plus a quality guarantee ('exact page order'). That distinguishes it from siblings like pdf_split or pdf_extract_pages without needing to name them, though it never explicitly states the boundary.

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 only implied by the verb: combine several PDFs into one. There is no statement of when to prefer this over alternatives, no prerequisites, and no mention of how base64Data relates to documentsBase64 as an input path (that precedence lives only in the schema).

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