Vacation region resolver — $0.010 per call (x402, USDC on Base). Resolve a Dutch place to its vacation region (noord/midden/zuid) and attach that region's current holiday dates.
| Name | Required | Description | Default |
|---|---|---|---|
| plaats | No | Place/city name. | |
| gemeente | No | Municipality name. | |
| postcode | No | Dutch postcode, e.g. 1011AC (resolved to gemeente/region). | |
| province | No | Province name. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are present, so the description carries the transparency burden. It discloses the per-call cost, the allowed region values, and the attach action, but does not specify input-resolution behavior (e.g., precedence among plaats, gemeente, postcode, province) or failure/response details.
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?
A single sentence that front-loads the tool's purpose and pricing, then states the action and output. Every phrase adds value with no 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 resolver with four optional identifier fields and no output schema, the description states high-level behavior but leaves ambiguity about which parameter(s) to provide and what the return payload looks like. It is serviceable but not fully complete for an agent to invoke reliably.
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?
Input schema covers all four parameters with descriptions (100% coverage), so baseline is 3. The description adds no additional parameter meaning beyond saying 'Dutch place' and does not clarify how the optional identifiers are prioritized or combined.
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?
Description uses specific verb 'resolve' with clear resource (Dutch place) and outputs (vacation region and current holiday dates). It distinguishes itself from sibling nl_school_holidays by focusing on vacation regions (noord/midden/zuid).
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 implies when to use (when a Dutch vacation region and associated holiday dates are needed) but provides no explicit when-not-to-use guidance or alternatives such as nl_school_holidays. Usage context is clear but exclusions are absent.
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.
Each tool targets a distinct data source or function: address lookup, building info, demographics, elevation, school holidays, vehicle lookup, validation, currency conversion, plus meta-tools for catalog and sample responses. There is no meaningful overlap between any pair of tools.
The Dutch-specific tools all follow a consistent 'nl_<subject>' pattern (nl_address, nl_building, etc.), and all names use snake_case. However, three tools (catalog, global_fx, sample) break the prefix pattern, creating a minor inconsistency but remaining clear and readable.
With 11 tools, the server is well-scoped for a Dutch open data API. Each tool covers a distinct data domain, and the count is within the ideal range without feeling excessive or sparse.
The tool surface covers a broad range of Dutch open data lookups, including addresses, buildings, demographics, elevation, holidays, and vehicles, along with validation and a sample mechanism. Minor gaps exist (e.g., no weather or property value data), but the core domain is well represented.