CHGIS MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_place_by_idB | Query historical place details by unique ID |
| search_placesC | Search places by name, year, administrative level, etc. |
| get_place_historical_contextB | Get historical context and hierarchical relationships of a place |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
Each tool has a clearly distinct purpose: get_place_historical_context retrieves context and relationships, search_place_by_id queries by ID, and search_places searches by multiple criteria. There is no overlap or ambiguity between these functions.
All tools follow a consistent verb_noun pattern with snake_case: get_place_historical_context, search_place_by_id, and search_places. The naming is predictable and uniform throughout the set.
With only 3 tools, the server feels thin for a historical geographic information system domain. While the tools cover core querying functions, the scope suggests potential gaps in operations like data creation, updates, or more specialized analyses.
The toolset is severely incomplete for a CHGIS server, lacking any CRUD operations beyond querying. There are no tools for creating, updating, or deleting place data, and no lifecycle coverage, which will likely cause agent failures in broader workflows.