Skip to main content
Glama
BoykoNeov

hike-finder

by BoykoNeov

find_hikes

Find marked hiking routes from OpenStreetMap within a bounding box, filtered by elevation gain, distance, loop or point-to-point shape, and car or chairlift access with locally computed metrics.

Instructions

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), circular (loop vs point-to-point), car_access (parking mapped near a trail end), chairlift_access (a ride-up aerialway — chairlift/gondola/cable car — mapped near a trail end). Boolean filters are tri-state: omit = don't care, true = require, false = exclude.

Confidence: shape (circular) is reliable. car_access/chairlift_access are best-effort from OSM completeness — a false means nothing of that kind is MAPPED near the route's ends, not that it is impossible to get there.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
southYes
westYes
northYes
eastYes
min_gain_mNo
max_gain_mNo
min_distance_kmNo
max_distance_kmNo
circularNotrue = loops only, false = point-to-point only.
car_accessNotrue = require parking mapped near an endpoint.
chairlift_accessNotrue = require a ride-up aerialway near an endpoint.
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description fully carries the burden of behavioral disclosure. It explains that data is from OSM, computed locally, that boolean filters are tri-state (omit, true, false), and provides confidence levels for shape, car_access, and chairlift_access. This is comprehensive and honest.

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 description is well-structured with clear sections and front-loads key information. It is slightly longer than necessary but every sentence contributes meaning. There is no wasted text.

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?

Given the complexity of 11 parameters and no output schema, the description provides thorough information about filters and data reliability. However, it does not explain the return format or pagination, which would be helpful. Overall, it is nearly complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 27%, but the description compensates by explaining the meaning of min/max gain and distance, the tri-state behavior of boolean filters, and the limitations of car_access/chairlift_access. For the bounding box parameters, they are self-explanatory. The description adds substantial value beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states it finds marked OSM hiking routes in a bounding box with filters for elevation gain, distance, shape, and access. The verb 'find' and the resource 'hiking routes' are specific, and no sibling tools exist to cause confusion.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides clear context about filters and data source, but does not explicitly state when to use this tool versus alternatives or when not to use it. Since no sibling tools are listed, the lack of explicit usage guidance is less critical, but still a slight gap.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/BoykoNeov/hike-finder-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server