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

gov_place_at_date

Read-only

Retrieves a Central European place’s historical name and civil chain to the state for a given year, flagging undated links and mid-year changes.

Instructions

A place as it was in one year: its name and the civil chain above it to the state.

Each level gives its type and the link's dates. Links GOV leaves undated, or attests only in another year, are marked. A place that changed Kreis or state within the year shows both. Reads up to 40 GOV objects the first time, then from the cache.

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_place_at_date"
  }
}

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').
languageNoPreferred language of names, as GOV codes it: 'deu', or 'pol' for a place under Polish rule then.deu

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 cover readOnlyHint and openWorldHint, so the description's value is what it adds: it discloses the first-call cost (reads up to 40 GOV objects) and subsequent cache reads, plus data-quality conventions (undated links and links attested only in another year are marked, mid-year Kreis/state changes show both chains). That is meaningful behavior beyond the structured fields, though it says nothing about failure modes for an unresolvable gov_id or an out-of-range year.

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 purpose is front-loaded in the first sentence and the remaining sentences each carry distinct information (level detail, marking rules, dual chains, caching). Some phrasing is dense and slightly oblique, e.g. 'Links GOV leaves undated, or attests only in another year, are marked', and the line breaks fragment clauses, but no sentence is filler.

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 shape, and it does: name, per-level type and link dates, marking of undated/other-year links, and dual chains on mid-year changes. It omits error behavior and any ordering or size expectations for the response, which is the remaining gap for a no-output-schema tool.

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%, including the gov_id id/URL/'system:ref' formats and the language code guidance, so the schema carries the parameter burden. The description reinforces the 'one year' semantics of the year parameter and the name output, but adds no syntax or format detail beyond the schema. Baseline 3 applies.

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 description states a specific resource and scope: a place's name plus the civil chain above it to the state, resolved for a single year, with per-level type and link dates. That is far more precise than the bare name 'gov_place_at_date'. It never contrasts itself with siblings such as gov_object or gov_search, so sibling differentiation is absent.

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: an agent can infer this is the call for a historical hierarchy at a specific year. There is no explicit when-to-use/when-not or pointer to gov_object for a single object versus this tool for the full chain. For a read tool with several plausible siblings, that routing guidance is the main gap.

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