Skip to main content
Glama
Adriapt

Hiking MCP Server

by Adriapt
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

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

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
get_routesA

Search for routes on Wikiloc based on geographical area.

Args:
    query: Search query (e.g. "Vall de Núria - Ribes de Freser").
    sw_lat: Latitude of the southwest corner of the bounding box.
    sw_lon: Longitude of the southwest corner of the bounding box.
    ne_lat: Latitude of the northeast corner of the bounding box.
    ne_lon: Longitude of the northeast corner of the bounding box.
    page: The page of results to fetch.
    max_results: The maximum number of results to return.


Output: 
    "title": Name of the trail,
    "url": Url,
    "distance_km": Distance in KM,
    "slope": Slope of the trail in meters,
    "author": Author of the trail,
    "location": Location of the trail,
    "trailrank": Punctuation of the trail.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A4.2/5.0

Scored across 1 tool

Disambiguation5/5

Only one tool exists, so there is no possibility of confusion between tools. The tool's purpose is clear and distinct.

Naming Consistency5/5

With a single tool, naming is internally consistent and follows a clear verb_noun pattern ('get_routes').

Tool Count2/5

The server contains only one tool, which feels too few for the apparent scope of a hiking server. Even if search is the core feature, users likely need additional operations like route details or filtering.

Completeness2/5

The server only offers route search, missing common operations for a hiking domain such as route detail retrieval, user favorites, or trip planning. This leaves significant gaps that will likely require workarounds.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources