onvaou-itineraires-mcp
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| OVO_API_KEY | Yes | Your OVO API key. Create a free API key at https://console.onvaou.app (10,000 requests per month, no credit card). |
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 |
|---|---|
| compute_routeA | Computes up to three routes (safe, balanced, fast) between two points in Europe for a bike, e-bike, kick scooter, motorcycle, wheelchair or on foot, with the share of cycle lanes, unpaved surfaces, main roads and motorways, the climb, and turn-by-turn steps. Use it to plan a safe cycling commute, compare a safe and a fast option, check wheelchair accessibility of a trip, or plan a motorcycle trip avoiding tolls or motorways. Coordinates are longitude/latitude: geocode addresses first. |
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
With only one tool, there is no ambiguity; the tool's purpose is clearly defined and distinct from any potential peers.
The single tool name 'compute_route' follows a clear verb_noun pattern and is descriptive, though there are no other tools to compare against.
A single tool feels insufficient for a routing service, especially since the description references geocoding as a prerequisite, which is not provided. A typical server would include at least geocoding and route management tools.
The server only covers route computation, but the workflow implies a need for geocoding (to get coordinates) and possibly route saving or sharing, which are absent. This creates a significant dead-end for agents.