Render an HTML document to a real PDF with headless Chrome (full CSS support, print backgrounds). 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 |
|---|---|---|---|
| html | Yes | Full HTML document to render | |
| format | No | A4 | |
| landscape | No |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full transparency burden. It discloses the rendering engine, CSS support, print backgrounds, 24-hour hosted download URL validity, demo limits, authentication method, and per-render cost. It does not cover data-handling or failure behavior, but the disclosed traits are substantial and useful.
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?
The description is concise and front-loaded: the core rendering behavior comes first, followed by the output URL expiry and then pricing/auth. The pricing sentence is long but dense with necessary details, so little is wasted.
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?
For a simple conversion tool, the description covers the essential input, output format and URL expiry, authentication, quotas, and cost. There is no output schema, so explaining the hosted download URL is appropriate. Minor gaps remain around error behavior and explicit parameter semantics, but the overall context is strong.
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 description coverage is only 33%, and the description adds no guidance about the format or landscape parameters beyond their names and defaults. It does repeat the html parameter concept but does not compensate for the low schema coverage with additional parameter-level meaning.
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 states a specific verb ('Render') and resource ('HTML document' to 'PDF'), with useful qualifiers like 'real PDF' and 'headless Chrome'. It does not explicitly differentiate from the sibling url_to_pdf, though the input type (HTML vs URL) is implied.
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 provides operational context such as the demo quota, API key requirement, and unit cost, but does not say when to prefer html_to_pdf over url_to_pdf or other siblings. No when-not-to-use or alternative routing guidance is given.
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.