hills-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 | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| find_nearby_hillsA | Find British and Irish hills near a location. Provide latitude and longitude coordinates. Returns hills sorted by distance, optionally filtered to one classification (e.g. only Munros). |
| search_hillsA | Search British and Irish hills by name. Returns ranked matches with height, county, and DoBIH number. |
| get_hill_detailsA | Get full details for one hill by name or DoBIH number: height, drop, grid reference, coordinates, county, classifications, and links. |
| get_listA | List all hills in a classification (Munros, Wainwrights, Corbetts, Marilyns...), sorted by height, with an optional height range filter. |
| get_hill_statsA | Overview of the hills database: total hills, counts per classification (Munros, Wainwrights...), and counts per country. |
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 5 tools
Each tool has a clearly distinct purpose: location-based search, name-based search, detail lookup, database stats, and classification listing. There is no overlap or ambiguity between them.
All tool names follow a consistent verb_noun pattern using snake_case (find_nearby_hills, search_hills, get_hill_details, get_hill_stats, get_list). While the verbs vary (find, search, get), the pattern is uniform and predictable.
With 5 tools, the server is tightly scoped to its purpose of querying a hills database. Each tool covers a distinct aspect of discovery and retrieval without superfluous additions.
The tool set covers the full lifecycle for a read-only reference database: discovery (find, search, list), detail viewing, and statistical overview. No obvious gaps exist for typical usage scenarios.