JobDoneBot

PDF Merge

pdf-join

Combine multiple PDFs into one with drag-to-reorder.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`pdfs`	Yes	Array of base64-encoded PDF files to merge (order preserved)

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

Changed3 schema fields changedFeb 21, 2026

addedInput schema / $schema

Added value: +"http://json-schema.org/draft-07/schema#"

addedInput schema / properties / pdfs

Added value: +{
+  "description": "Array of base64-encoded PDF files to merge (order preserved)",
+  "items": {
+    "type": "string"
+  },
+  "maxItems": 50,
+  "minItems": 2,
+  "type": "array"
+}

addedInput schema / required
```
Added value: +[
+  "pdfs"
+]
```

First observedFeb 14, 2026

TDQS

A3.7/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full burden. It discloses the drag-to-reorder interaction but omits important behavioral details such as input format (base64), limits (2-50 files), and whether the operation creates a new file or modifies existing ones. It does not contradict annotations, but it leaves significant gaps.

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?

The description is a single sentence that front-loads the action and key feature. Every word earns its place, with no redundancy or filler.

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

Completeness3/5

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

For a simple one-parameter tool with no output schema, the description is adequate but minimal. It does not mention output format, file size considerations, or that the merged PDF is downloaded. However, the schema covers the input, so the description is acceptably complete for basic use.

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 description coverage is 100%: the only parameter 'pdfs' is clearly described with type, format (base64-encoded PDFs), and order preservation. The description adds no additional parameter-specific insight, but the schema already does the heavy lifting, meeting the baseline.

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 uses a specific verb ('Combine') and resource ('multiple PDFs into one'), clearly distinguishing this tool from siblings like pdf-split or pdf-compress. The mention of 'drag-to-reorder' adds a distinctive feature, making the purpose unmistakable.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies when to use the tool: whenever a user needs to merge PDFs. While it doesn't explicitly name alternatives or exclusions, the clarity of 'Combine multiple PDFs into one' provides sufficient context for selection among the many PDF-related sibling tools.

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

All JobDoneBot tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

B3.1/5.0

Disambiguation2/5

Multiple tools have overlapping purposes, such as bg-remover, bg-remover-pro, pro-matting, and takumi all performing background removal, and upscaler/upscaler-pro being redundant. With 202 tools, an agent may easily select the wrong one despite detailed descriptions.

Naming Consistency4/5

Most tools use a consistent kebab-case format with descriptive names like pdf-compress, image-resizer, and tax-return-calc. Exceptions like 'takumi', 'pro-matting', and '-pro' suffixes (bg-remover-pro, upscaler-pro) are minor deviations relative to the total.

Tool Count1/5

202 tools is an extreme mismatch for an MCP server, far exceeding the typical 3-15 well-scoped range. The sheer volume makes it unwieldy for an agent to efficiently navigate and select the right tool.

Completeness4/5

The tool set provides extensive coverage across many domains, including PDF operations (20+ tools), image editing, financial calculations, e-commerce fee estimation, and YouTube utilities. Minor gaps exist in cross-tool integration, but the breadth is highly comprehensive for the apparent purpose.

Resources

Need Help?