route-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ROUTE_MCP_GOOGLE_MAPS_API_KEY | Yes | Google Maps Platform API key with the Routes API enabled. Required for route comparison tools. |
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
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| compare_routesA | Compare door-to-door travel time by bicycle, motorbike and public transport (metro, RER, bus, tram) between two places in Île-de-France. Motorbike times are estimates. |
| get_weatherA | Current weather and hourly forecast (temperature, rain, wind) for a place in Île-de-France. |
| find_placeA | List the best matching places in Île-de-France for an address or name. Use it when a place is ambiguous, before comparing routes. |
| get_api_usageA | How many metered API calls are used and remaining in the current period, per budget. |
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 4 tools
Each tool has a clearly distinct purpose: place lookup, route comparison, weather lookup, and API usage monitoring. There is no meaningful overlap between any of the tools.
All tools follow a consistent verb_noun pattern: compare_routes, get_weather, find_place, get_api_usage. The naming convention is uniform and predictable.
Four tools is a reasonable, focused scope for a routing assistance server. Each tool serves a necessary function and none feel redundant or excessive.
The core workflow is covered: find a place, compare routes, and optionally check weather. Minor gaps exist such as lack of route detail endpoints or alternative route options, but the essential use case is well supported.