hike-finder
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HIKE_DEM_DIR | No | Directory containing GeoTIFF DEM tiles (for local or auto mode). | |
| HIKE_CAR_RADIUS | No | Radius in metres to search for parking near trail ends. | 300 |
| HIKE_LIFT_RADIUS | No | Radius in metres to search for lift stations near trail ends. | 400 |
| HIKE_OVERPASS_UA | Yes | User-Agent for Overpass API. Required by the public server; set to a real email or project URL. | |
| HIKE_API_ENDPOINT | No | Override the elevation API endpoint. | |
| HIKE_OVERPASS_URL | No | Override the Overpass endpoint (use a regional/self-hosted instance for heavy use). | https://overpass-api.de |
| HIKE_SMOOTH_WINDOW | No | Elevation smoothing window size in samples. | 3 |
| HIKE_ELEVATION_MODE | No | Elevation mode: 'api', 'local', or 'auto'. | auto |
| HIKE_GAIN_THRESHOLD | No | Hysteresis climb threshold in metres. | 10 |
| HIKE_LOOP_TOLERANCE | No | Distance (in metres) between start and end to consider a loop. | 150 |
| HIKE_SAMPLE_INTERVAL | No | Resample spacing along the track in metres. | 25 |
| HIKE_MAX_ROUTE_FACTOR | No | Maximum route length factor relative to bbox diagonal; drops through-routes. | 4.0 |
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": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| find_hikesA | Find marked OSM hiking routes in a bounding box, filtered by real computed elevation gain and distance, plus shape and access. Data is OpenStreetMap route relations (same source family as mapy.cz); gain/distance are computed locally, not scraped. Filters (all optional): elevation gain (m), distance (km), Confidence: shape (circular) is reliable. car_access/chairlift_access are best-effort from OSM completeness — a |
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 1 tool
Only one tool exists, so there is no possibility of confusion between tools. The agent will always choose the correct tool.
With a single tool, naming consistency is automatically maintained. The verb_noun pattern is clear and descriptive.
The server has only one tool, which feels thin for a typical MCP server. While the tool is comprehensive, a single tool often suggests missing functionality or potential for better scoping.
The tool covers the core 'find hikes' use case with many filters (elevation, distance, circular, access). Minor gaps exist, such as lacking a tool to retrieve detailed info for a specific hike or to manage user preferences, but the search functionality is robust.