Skip to main content
Glama
jacquesfize

GeoTrek MCP

by jacquesfize
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
MCP_HOSTNoThe host address for streamable-http.0.0.0.0
MCP_PORTNoThe port for streamable-http.8000
MCP_TRANSPORTNoThe MCP transport: stdio or streamable-http.stdio
NOMINATIM_URLNoThe Nominatim instance to use for geocoding.https://nominatim.openstreetmap.org
GEOTREK_BASE_URLYesThe base URL of the GeoTrek instance.

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
list_activitiesB

Liste les types d'activité (pratiques) disponibles sur l'instance GeoTrek configurée (ex : "A pied", "VTT", "Cheval", "Raquette"...).

Les noms retournés peuvent être utilisés tels quels dans le paramètre practice_names de l'outil search_treks.

list_labelsA

Liste les labels de réglementation disponibles sur l'instance GeoTrek configurée (ex : "En coeur de parc", "Chiens de protection des troupeaux"...).

Les noms retournés peuvent être utilisés tels quels dans le paramètre label_names de l'outil search_treks.

search_treksA

Recherche des treks (randos, VTT, ...) sur l'instance GeoTrek configurée.

Filtres disponibles : durée en heures (duration_min_h/duration_max_h), dénivelé positif en mètres (ascent_min_m/ascent_max_m), réglementation (label_names, noms tels que renvoyés par list_labels), type d'activité (practice_names, noms tels que renvoyés par list_activities), et proximité géographique soit par nom de lieu (place, géocodé via Nominatim) soit par coordonnées directes (lat/lon), combinée à un rayon de recherche radius_km (défaut 10 km).

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

A3.9/5.0

Scored across 3 tools

Disambiguation5/5

Each tool has a distinctly different purpose: listing activities, listing labels, and searching treks. There is no overlap or potential for misselection.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern in snake_case (list_activities, list_labels, search_treks), making the API predictable.

Tool Count4/5

Three tools is a minimal but appropriate set for a search-focused server. Each tool is needed to support the core search workflow, though the count is at the lower boundary of the typical range.

Completeness4/5

The core workflow of listing valid filter values and searching treks is fully covered. Minor gaps exist, such as lack of a dedicated get-trek-by-id tool, but search likely returns full trek details, so agents can work around this.

Maintenance

ActivitySlowing
ResponsivenessNo issues

Resources