Merge multiple PDFs into a single PDF, preserving the given order.
| Name | Required | Description | Default |
|---|---|---|---|
| output_name | No | Name for the merged PDF. | merged.pdf |
| source_urls | No | Public URLs of the PDFs to merge, in order (minimum 2). | |
| files_base64 | No | Base64-encoded PDFs to merge, in order (minimum 2). Use when there are no URLs. |
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations indicate idempotent and open-world behavior, which are consistent. The description adds that order is preserved, but does not disclose error handling, required minimum count (2 PDFs), or whether the result is a file or path. The value added beyond annotations is modest.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single, front-loaded sentence that captures all essential information without wasted words. Every part adds value.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given an output schema exists (context signal), the description adequately covers the core function. It is missing minor context about source selection and prerequisites, but is sufficient for a simple tool.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100%, so the schema already documents all three parameters. The description provides no additional parameter-level details beyond what is in the schema descriptions; baseline 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description uses a specific verb ('merge') and resource ('PDFs'), states the outcome ('single PDF'), and adds the key behavior of preserving order, which clearly distinguishes it from sibling tools like split_pdf or compress_pdf.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies the tool is for merging PDFs but provides no explicit guidance on when to use it vs alternatives, nor does it explain when one parameter source (URLs vs base64) is preferred over the other.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool has a clearly distinct purpose, covering different file operations (compress, convert, extract, merge, split, etc.) and billing management. No two tools overlap in functionality.
Most tool names follow a verb_noun pattern (compress_image, protect_pdf), but a few deviate (images_to_pdf, list_supported_conversions) causing minor inconsistency. The pattern is largely predictable.
17 tools is slightly above the typical well-scoped range, but still reasonable given the breadth of file manipulation and billing operations. Each tool serves a distinct need.
The file conversion and PDF manipulation operations are well-covered (compress, convert, extract, merge, split, protect, etc.). The billing tools are complete for subscription and credit management. Minor gaps exist, such as batch operations or image format conversions.