Travel Planning FastMCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DASHSCOPE_API_KEY | Yes | API key for DashScope (Tongyi Qwen). Required for plan_trip_route_tool. |
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
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| plan_trip_route_toolC | Plan a multi-day route with Qwen-Agent, including daily food recommendations. |
| plan_trip_route_local_toolB | Plan a deterministic offline route with daily food recommendations. |
| estimate_trip_budget_toolB | Estimate lodging, food, transport, attractions, and contingency costs. |
| suggest_packing_list_toolA | Suggest packing items for a destination, season, and activity mix. |
| recommend_food_experiences_toolC | Recommend food districts, meal themes, and dietary notes. |
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 5 tools
The two route planning tools are clearly differentiated by their execution mode (Qwen-Agent vs local deterministic), but their overlapping names and similar outputs could cause occasional confusion. The remaining tools (budget, packing, food) are clearly distinct.
All tool names follow a consistent verb_noun_tool pattern in snake_case, making the API predictable and easy to navigate.
At five tools, the server is well-scoped for travel planning, covering route, budget, packing, and food without unnecessary bloat.
The core trip planning lifecycle is covered (route, budget, packing, food), but there's no explicit activity/attraction planning or weather integration, leaving minor gaps.