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.
| Name | Required | Description | Default |
|---|---|---|---|
| urls | Yes | Public URLs of the PDFs, in merge order |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full behavioral burden and does so thoroughly: it discloses the auth header format, demo rate limit (3/day), unit cost (25 units/render), and that the result is a hosted URL expiring in 24 hours. This goes well beyond typical descriptions.
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?
Three tight sentences deliver all needed information: core operation, output behavior, and usage/cost constraints. No filler or redundant restating of the tool name.
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 no output schema and no annotations, the description adequately covers return value, URL validity window, input limits, authentication, and cost. An agent has enough to select and invoke this tool correctly.
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?
The schema already fully documents the 'urls' parameter with min/max items, max length, and merge-order explanation, so baseline is 3. The description adds value by specifying a 10MB per-file cap and requiring public URLs, extending meaning beyond the schema.
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 starts with a specific verb and resource: 'Merge 2-10 PDFs ... into one PDF'. It clearly distinguishes itself from sibling conversion tools like html_to_pdf and url_to_pdf by specifying the merge operation and input constraints.
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 gives clear context for when to use this tool: when merging 2-10 publicly accessible PDF URLs, with explicit size and count limits. It does not explicitly name alternatives or exclusion cases, so it falls just short of a 5.
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.
Most tools have clearly distinct purposes, but some pairs could be confused: html_to_pdf vs url_to_pdf both produce PDFs, read_page vs url_screenshot both fetch a URL, and generate_test_bsn vs generate_brp_test_data both generate Dutch test data. Detailed descriptions mitigate most ambiguity, so agents can usually select correctly.
All tool names follow a consistent snake_case convention with predictable verb_noun patterns (e.g., generate_*, validate_*, memory_*, url_*). The naming is uniform and makes each tool's function easily inferable from its name.
35 tools is a heavy surface for any MCP server, even a general-purpose toolbox. The large number of niche Dutch-specific tools (BRP, UPA, BSN, holidays) may overwhelm agents and increase selection complexity. The server could benefit from splitting into smaller, focused servers.
The server covers a wide range of utilities, but there are notable gaps: no hash generation, no json_to_csv counterpart, and the workflow sub-domain only offers list/run without create/delete. Core utilities are present, but some obvious counterparts and lifecycle operations are missing.