Geo-Insights Environmental Data

Lookup Municipality

lookup_municipality

Read-onlyIdempotent

Find Dutch municipalities by name or province.

Returns CBS codes needed for other tools (get_policy_requirements,
rank_measures). All 342 Dutch municipalities are searchable.

Args:
    name: Partial name match (e.g. "Rotter" finds Rotterdam)
    province: Filter by province name (e.g. "Zuid-Holland")

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "lookup_municipality"
  }
}

Input Schema

Name	Required	Description	Default
`name`	No
`province`	No

Output Schema

Name	Required	Description	Default
`count`	Yes
`municipalities`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 14, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and non-destructive behavior, so the safety profile is covered. The description adds useful context beyond that: the closed dataset size (342 municipalities) and the fact that it returns CBS codes used elsewhere. It omits edge-case behavior such as no-match results or whether both filters can be combined.

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?

Purpose and dependency are front-loaded in two short sentences before the Args block, and every line adds information. The Args formatting is slightly redundant with the schema property names, but the embedded examples earn their space.

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?

For a simple two-optional-parameter lookup with an output schema and full annotations, the description covers purpose, dataset scope, downstream use, and both parameters. Only default behavior with zero arguments and no-match handling are unaddressed, which is a minor gap here.

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 carries the burden, and it does document both parameters with concrete examples ('Rotter' finds Rotterdam; province 'Zuid-Holland'). It does not clarify combination semantics (AND vs override), case sensitivity, or accent handling, which keeps it below a 5.

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?

States a specific verb and resource ('Find Dutch municipalities') and immediately scopes the dataset ('All 342 Dutch municipalities'). It also names the downstream consumers (get_policy_requirements, rank_measures), so an agent knows exactly where this tool sits relative to siblings.

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?

The line 'Returns CBS codes needed for other tools (get_policy_requirements, rank_measures)' effectively signals this is a prerequisite lookup to run before those tools. It does not state explicit exclusions or what to do when a lookup fails, so it stops short of a 5.

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?