Skip to main content
Glama

AstraNL Coordination Protocol

nl_municipal_build_rules

Read-onlyIdempotent

Dutch municipal rules for a renovation or building job, with ONE read-only call. Give a municipality, optionally the planned bouwkosten excluding VAT. Returns the 2026 omgevingsvergunning fee, leges, for the technical building activity as the municipality's own regulation sets it, and whether a skip or container on the public road needs a permit, a notification or nothing, with the permit fee and precario where confirmed. Every answer names the regulation, article and source URL, the read date and how it was verified. Coverage: all 342 municipalities for leges, 296 for containers. Limits: the municipality decides; spatial or other permit parts are not added; a fee is withheld when the tariff is not verified. Free, no auth, no side effects.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "municipality": "<municipality>"
    },
    "name": "nl_municipal_build_rules"
  }
}

Input Schema

NameRequiredDescriptionDefault
municipalityYesDutch municipality name or CBS code, e.g. Zaanstad or GM0479
bouwkosten_eurNoplanned construction cost excluding VAT in euro; default 50000

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, yet the description still adds real behavior: free, no auth, no side effects, 342-municipality coverage for leges versus 296 for containers, fees withheld when a tariff is unverified, and per-answer provenance (regulation, article, source URL, read date, verification method). The withheld-fee rule is exactly the kind of caveat an agent needs before presenting a number as authoritative.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The key output (fee plus container rule) is front-loaded and every sentence carries information — coverage counts, limits, provenance. The only waste is the closing 'Free, no auth, no side effects', which largely repeats what readOnlyHint and openWorldHint=false already convey.

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

Completeness4/5

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

With no output schema, the description carries the full burden of describing returns, and it does: fee, container outcome (permit/notification/nothing), permit fee, precario, and provenance fields. The remaining gap is behavior for the 46 municipalities lacking container coverage — the agent is told a fee is withheld when unverified but not what the container answer looks like when uncovered.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so both parameters (municipality accepting a name or CBS code, bouwkosten_eur with a 50000 default) are already documented. The description only restates that bouwkosten is optional and excludes VAT, adding no syntax, format or edge-case detail beyond the schema. Baseline 3 applies when the schema carries the load.

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 names a specific verb and resource: it returns the 2026 omgevingsvergunning fee (leges) for the technical building activity set by a municipality's own regulation, plus the skip/container permit status on public roads. That is far more specific than the tool name, and an agent can tell it apart from every sibling (cost, offer, counterparty tools) without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is explicitly framed: supply a municipality and optionally the planned bouwkosten excluding VAT, for a renovation or building job. The exclusions are stated too — spatial or other permit parts are not added — which tells the agent when this tool's answer is incomplete. It stops short of a 5 because no explicit routing to an alternative is given, though no sibling plausibly covers this domain.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources