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

gov_registers

Read-only

Find which parish and Standesamt kept a place's registers in a given year, plus the archive bodies and local court above each parish, as GOV records them.

Instructions

Which parish and Standesamt kept a place's registers in one year, as GOV records it.

Looks at the place and every level above it in that year; each lead says which level carries the link, with dates. Gives the bodies above each parish (whose archive may hold the books) and the local court. Says plainly when GOV records no parish or Standesamt. A link is a lead: confirm it in the register's own heading.

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": {
      "gov_id": "<gov_id>",
      "year": "<year>"
    },
    "name": "gov_registers"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearYesThe year of the event, e.g. 1885.
gov_idYesA GOV id (e.g. 'QUEURGJO51NT', 'object_289891'), its GOV page address, or an external id GOV records as 'system:ref' (e.g. 'geonames:2851465', 'wikidata:Q40623').
confessionNoKeep parishes of one confession: protestant, lutheran, reformed, catholic, old catholic or jewish (or GOV's codes ev, lu, lt, rf, rk, ak).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so safety is covered; the description adds real behavior: it walks the place and every level above it for that year, reports which level carries each link along with dates, returns the bodies above each parish and the local court, and explicitly signals when GOV records no parish or Standesamt. The caveat that links are leads requiring confirmation in the register's own heading is valuable epistemic context. Minor gaps remain on result shape/ordering, keeping it at 4.

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 core answer is front-loaded in the first sentence and the remaining sentences each carry distinct information (scope of traversal, what leads contain, absence signaling, confirmation caveat). Some phrasing is slightly literary and could be tightened, but nothing is pure 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?

With no output schema, the description must convey return content, and it does: hierarchical leads with the level carrying the link, dates, supervising bodies, the local court, and explicit no-record signaling. What is missing is format granularity (field names, whether results are grouped per level or flat), which would matter for a tool whose output is a structured hierarchy.

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 all three parameters are already documented in the schema, including accepted GOV id forms and confession values; the baseline is 3. The description only lightly reinforces semantics ('in one year', 'the place and every level above it in that year') and never mentions the confession filter, so it adds little beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The opening states a specific question answered: which parish and Standesamt kept a place's registers in a given year, per GOV records. That is a clear resource-plus-outcome, not a restatement of the name. It does not explicitly distinguish itself from the sibling gov_place_at_date, which appears to share the 'place hierarchy at a date' traversal, so it falls short of a 5.

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

Usage Guidelines3/5

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

Usage is implied rather than stated: the tool is for answering register-responsibility questions for a place and year, and the closing line 'A link is a lead: confirm it in the register's own heading' tells the agent how to treat results. There is no explicit when-to-use/when-not or named alternative (e.g. versus gov_place_at_date or gov_search), so the agent must infer routing.

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