wheels-router-mcp
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
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
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| plan_tripA | Plan a transit trip. Uses Wheels Router for Hong Kong and Transitous for other regions. IMPORTANT: fares_min/fares_max are fare ranges, NOT interchange discounts. Interchange discounts (轉乘優惠) only apply when FareDiscountRules are explicitly present in the API response, and IT ONLY APPLIES TO CERTAIN ROUTES. |
| search_locationA | Search locations via Nominatim (use for origin/destination lookup). |
| hello_toolD | Hello tool |
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 3 tools
plan_trip and search_location have clear, non-overlapping purposes, and hello_tool is obviously set apart. However, hello_tool is a vague stub that doesn't fit the travel domain, so there is a slight coherence cost.
plan_trip and search_location both follow a verb_noun snake_case pattern. hello_tool breaks the pattern with a greeting-style verb, but since only one of three tools deviates, the naming is mostly consistent.
Three tools is borderline for a transit router, and only two are actually useful. hello_tool is filler, which makes the effective functional surface feel thin for the stated purpose.
The core workflow is covered: search_location for origin/destination lookup and plan_trip for routing. Minor gaps exist, such as route/fare rule inspection or provider metadata, but agents can complete basic trip planning without dead ends.