toolforte

Merge PDFs

pdf_merge

Merge 2-10 PDFs (public URLs, max 10MB each) into one PDF. Returns a hosted download URL valid for 24 hours. Free demo: 3 renders/day. With a free ToolForte API key (Authorization: Bearer tf_..., get one at https://toolforte.com/developers), which spends your monthly unit balance: 25 units per render.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`urls`	Yes	Public URLs of the PDFs, in merge order

Output Schema

TableJSON Schema

Name	Required	Description
`url`	No	Hosted download URL of the produced file
`bytes`	No	Size in bytes
`result`	No	The result, when it is not an object
`metering`	No	What this call cost and what allowance remains
`expiresAt`	No	When the download URL stops working (ISO 8601)
`contentType`	No	MIME type of the produced file

Schema Changelog

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

Changed1 schema field changedSep 5, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "additionalProperties": {},
+  "properties": {
+    "bytes": {
+      "description": "Size in bytes",
+      "type": "number"
+    },
+    "contentType": {
+      "description": "MIME type of the produced file",
+      "type": "string"
+    },
+    "expiresAt": {
+      "description": "When the download URL stops working (ISO 8601)",
+      "type": "string"
+    },
+    "metering": {
+      "additionalProperties": {},
+      "description": "What this call cost and what allowance remains",
+      "properties": {
+        "remaining": {
+          "type": "number"
+        },
+        "source": {
+          "type": "string"
+        }
+      },
+      "type": "object"
+    },
+    "result": {
+      "description": "The result, when it is not an object"
+    },
+    "url": {
+      "description": "Hosted download URL of the produced file",
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

First observedSep 1, 2026

TDQS

A4.5/5.0

Behavior5/5

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

The description goes well beyond the annotations by disclosing the hosted download URL expiry (24 hours), the free demo quota (3 renders/day), the required Authorization header format, and the cost per render (25 units). This gives the agent a realistic picture of side effects, rate limits, and authentication needs.

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 compact and front-loaded: the core operation and constraints come first, followed by output behavior, then authentication and quota details. Every sentence contributes necessary information without fluff or repetition.

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

Completeness5/5

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

Given the single parameter, the existing schema coverage, and the presence of an output schema, the description provides all essential context: input constraints, output format, authentication, quotas, and pricing. An agent has enough information to decide whether to call the tool and how to format the invocation.

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?

The schema already documents the urls parameter with min/max items and merge order, so the baseline is 3. The description adds meaningful constraints not present in the schema, specifically the 10MB size limit per PDF and the 2-10 count range, which helps the agent validate inputs before calling.

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 ('Merge'), a specific resource ('2-10 PDFs'), and the outcome ('into one PDF'). It clearly distinguishes this from sibling tools such as pdf_split, images_to_pdf, and html_to_pdf by emphasizing merging existing PDFs from URLs.

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?

The description implies usage whenever PDFs need to be merged and gives concrete constraints (public URLs, 10MB limit, 2-10 files). However, it does not explicitly describe when to prefer this tool over related siblings like pdf_split or images_to_pdf, nor does it state any exclusions.

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

All toolforte 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

A3.8/5.0

Disambiguation5/5

Every tool targets a distinct resource or action, and the detailed descriptions clearly separate near neighbors like generate_test_bsn versus generate_brp_test_data, read_page versus url_screenshot versus url_to_pdf, and image_compress/convert/resize. Even with 40 tools, there is no real boundary-blurring overlap.

Naming Consistency3/5

All names are snake_case and readable, but the set mixes conventions: verb_noun (generate_*, validate_*), noun_verb (pdf_merge, image_resize), conversion-style names (csv_to_json, html_to_pdf), and bare nouns (base64, qr_code_png). The groups are recognizable, but there is no single predictable pattern.

Tool Count2/5

Forty tools is an oversized surface for an agent to consider on every call, well above the point where tool selection cost starts to hurt. The broad purpose explains the count, but many one-off utilities could be grouped or exposed selectively.

Completeness3/5

The server covers many domains—encoding, Dutch test data, image/PDF handling, memory, and workflows—but several categories are partial: there are no reverse conversions like json_to_csv or html_to_markdown, no PDF text extraction, and no workflow create/update/delete tools. Agents can work around some gaps, but notable operations are missing.

Resources

Need Help?