Skip to main content
Glama
Sign In
gov-gazetteer-mcp

gov-gazetteer-mcp

by ianderso
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

gov_enclosures

Read-only

Retrieve dated enclosure chains for a place and its civil parents to build a dated place tree, with optional year filters and Gramps place type suggestions.

Instructions

Every dated enclosure of a place and of each civil place above it, for a place tree.

For each place: its names and types with dates, a suggested Gramps place type, and enclosed_by, one entry per parent with its periods, current first, each with a gramps_date ('from 1871-01-01 to 1937-03-31'). Parishes, courts and registry offices of the place come separately. Narrow with from_year/to_year; at most 40 places.

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

Input Schema

NameRequiredDescriptionDefault
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').
to_yearNoOnly enclosures that held in or before this year.
from_yearNoOnly enclosures that held in or after this year.

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 only declare readOnly and openWorld; the description adds real behavior beyond that: ancestor traversal for civil places, a 40-place cap, the shape of enclosed_by (one entry per parent, current period first), and the gramps_date string format. It still does not say what happens when the cap is exceeded or when gov_id is invalid.

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 and every subsequent sentence adds information about output structure or limits; nothing is filler. It is dense and jargon-heavy ('civil place', 'Gramps place type'), which slightly hurts skimmability for an unfamiliar agent.

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 does the work of describing the return payload (names/types with dates, suggested Gramps type, enclosed_by periods, gramps_date format), which is appropriate for this complexity. Remaining gaps are edge-case behavior at the 40-place limit and on invalid IDs.

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 coverage is 100% and each parameter already has a precise description, so the schema carries the load. The description's only addition is 'Narrow with from_year/to_year', which merely restates the filter intent without new semantics (e.g. inclusive boundaries or behavior when from_year > to_year).

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: every dated enclosure of the given place plus each civil place above it, returned as a place tree. That is concrete enough to separate it from siblings like gov_object or gov_place_at_date, though the verb is only implied ('Every dated enclosure...') rather than stated.

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?

It gives a narrowing instruction ('Narrow with from_year/to_year; at most 40 places') and notes that parishes, courts and registry offices 'come separately', which implicitly signals other endpoints. It never explicitly names an alternative or states when not to use this tool.

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

Deploy Server

Other Tools