Generate a QR code as a downloadable PNG image. 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 |
|---|---|---|---|
| size | No | ||
| text | Yes | Text or URL to encode |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full disclosure burden and does well: it reveals the return format, the 24-hour URL expiration, the 3-render/day demo cap, the auth header format, and the unit cost. This is rich behavioral detail beyond the schema.
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 three sentences, front-loaded with the primary purpose, then concisely covering output expiry, demo limits, and authentication requirements. Every sentence earns its place without redundancy.
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 two-parameter generation tool, the description is nearly complete: it explains output, lifetime, auth, and cost. The only notable omission is a clearer explanation of the size parameter's semantics, but this is a minor gap.
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 text parameter is already described in the schema as 'Text or URL to encode', and the description adds no new parameter-level meaning. The size parameter is not described in either place, though its name, default, and min/max constraints make its likely meaning inferable.
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 clearly states that the tool generates a QR code as a downloadable PNG and returns a hosted download URL. This distinguishes it from the sibling tools, none of which claim QR code generation.
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 usage context including the demo limit, API key requirement, and per-render cost. It does not explicitly mention when not to use it, but since no sibling tool offers QR generation, exclusions are less necessary.
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.