Geo-Insights Environmental Data

Get Municipality Policy Requirements

get_policy_requirements

Read-onlyIdempotent

Get BGI policy requirements for a Dutch municipality.

Extracted from Officiele Bekendmakingen (official government publications).
Shows what's required, recommended, or subsidized per gemeente.

Args:
    gemeente_code_or_name: CBS code (e.g. "GM0599") or municipality name
                          (e.g. "Rotterdam"). Use lookup_municipality to find codes.
    measure_slug: Optional — filter to one measure's requirements

Returns requirements grouped by type (subsidy, regulation, obligation)
with document titles, dates, amounts, and source URLs.

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": {
      "gemeente_code_or_name": "<gemeente_code_or_name>"
    },
    "name": "get_policy_requirements"
  }
}

Input Schema

Name	Required	Description	Default
`measure_slug`	No
`gemeente_code_or_name`	Yes

Output Schema

Name	Required	Description	Default
`count`	Yes
`last_updated`	No
`requirements`	Yes
`gemeente_code`	Yes
`gemeente_name`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 14, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, open-world behavior, so safety is covered. The description adds useful context the annotations lack — the official-publication provenance and how results are grouped by requirement type. It says nothing about rate limits, freshness, or empty-result behavior, which keeps it from a 5.

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?

Content is front-loaded with purpose, then source, then parameters, then return shape. The Args/Returns scaffolding is slightly verbose for two parameters but each line carries information an agent needs.

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

Completeness5/5

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

The tool is a simple two-parameter read with an output schema, and the description covers the input formats, the prerequisite lookup call, and the source of the data. There is nothing an agent needs in order to invoke it correctly that is missing.

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

Parameters4/5

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

Schema description coverage is 0%, so the description must carry the load, and it does: it gives CBS code and name formats with concrete examples ("GM0599", "Rotterdam") and marks measure_slug as an optional single-measure filter. The notion of a "slug" is not illustrated by example, leaving a minor gap.

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 (get BGI policy requirements) plus scope (a Dutch municipality) and the underlying source (Officiele Bekendmakingen). An agent can distinguish it from siblings like get_measure_detail or search_bgi_measures without opening a 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?

It gives a clear routing rule: use lookup_municipality to resolve the gemeente code, and describes the optional measure_slug narrowing. It does not explicitly state when to prefer get_measure_detail or get_context_summary instead, so it stops short of full alternatives coverage.

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

All Geo-Insights Environmental Data tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?