Skip to main content
Glama

Find a Dutch municipality

find_municipality
Read-onlyIdempotent

Find the URL slug of a Dutch municipality (gemeente) by name, for the other tools. Returns at most 10 matches with their province and the Klusvang page.

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

Input Schema

NameRequiredDescriptionDefault
nameYesPart of the name, e.g. Den Bosch or Nijmegen.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint=false, so the safety profile is covered. The description adds value beyond them by disclosing result cardinality ('at most 10 matches') and the returned fields ('province and the Klusvang page'), which matters since no output schema exists. It does not say what an empty result looks like.

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

Conciseness5/5

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

Two sentences, front-loaded with the action and output, and every clause carries information: resource, disambiguation gloss, consumer, result cap, and returned fields. No padding.

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 one-parameter lookup with annotations and no output schema, the description covers input meaning, result cap, and returned fields. Only the zero-match behavior is unaddressed, which is a small gap.

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 description coverage is 100% and the single parameter already documents partial-name input with examples ('Den Bosch or Nijmegen'). The description's 'by name' adds nothing beyond the schema, so the baseline 3 applies.

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 the URL slug of a Dutch municipality (gemeente) by name') and names the exact output artifact (the slug). The clause 'for the other tools' distinguishes it as a name-resolution step feeding the sibling permit-count tools rather than a data-returning analysis tool.

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?

'for the other tools' makes the intended workflow explicit: call this first to turn a municipality name into the slug other tools need. There is no stated when-not case (e.g., what to do if zero matches are returned), but for a single-purpose resolver the context is clear.

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