Skip to main content
Glama
gov-gazetteer-mcp
by ianderso

gov_search

Read-only

Find GOV place records by name to get IDs, types, coordinates, and current parent units; narrow results by enclosing district or place type before checking historical details.

Instructions

Find places in GOV by name: id, names, types, coordinates and current parents.

Matching is literal: whole words and word beginnings, ignoring case and accents (Lubeck finds Lübeck), never spelling variants. German, Polish and old spellings (Cöslin/Köslin/Koszalin) each need their own call, and a zero covers only the spelling tried. GOV answers at most 500 objects; use within or place_type to narrow. Then call gov_place_at_date with the event's year.

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": "gov_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesA place name, e.g. 'Quedlinburg'. One spelling per call.
limitNoMost candidates returned (1-100).
withinNoOnly places GOV records inside this object at any date: a GOV id of a Kreis, province or state, e.g. 'adm_133152'.
refreshNoAsk GOV again instead of the 7-day cache.
place_typeNoKeep these types: ids, GOV's German names ('Dorf', 'Kirchspiel', 'Standesamt'), or settlement, civil, parish, standesamt, court; comma-separated.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior5/5

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

Goes well beyond the readOnlyHint/openWorldHint annotations: it discloses the literal matching algorithm, case/accent folding rules, the exclusion of spelling variants, the meaning of an empty result, the 500-object server cap, and implicitly the 7-day cache via `refresh`. These are precisely the behavioral traits an agent cannot infer from the annotations or schema.

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?

Front-loads the purpose, then delivers matching behavior, then the narrowing strategy, then the next-step routing — a logical escalation with no filler sentences. Every clause carries operational information.

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 compensates by naming the returned fields, and it covers paging limits, cache behavior and the follow-up call. What is missing is a note on result ordering or how to read a partial versus complete match set for multi-word names.

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%, so baseline is 3. The description reinforces the semantics of `name` (one spelling per call) and the narrowing purpose of `within`/`place_type`, but it does not add syntax or format detail beyond what the schema already supplies for `limit` and `refresh`.

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 places in GOV by name') and even enumerates the payload (id, names, types, coordinates, current parents). The name-lookup framing clearly separates it from gov_place_at_date (date resolution) and gov_object (single-object retrieval), which the description also points to.

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?

Gives concrete usage conditions: one spelling per call, separate calls for German/Polish/old spellings, and narrowing via `within` or `place_type` when the 500-object cap is hit. It also chains forward to gov_place_at_date with the event's year, but never states when NOT to use this tool (e.g., when you already have a GOV id and should use gov_object).

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