Trip Planner
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PLANNER_MODEL | No | Optional model identifier for the planner agent. Defaults to whatever the provider uses. | |
| OPENAI_API_KEY | Yes | API key for OpenAI (or another provider via PLANNER_MODEL). Required. | |
| TAVILY_API_KEY | Yes | API key for Tavily search used by the Scout agent. Required. |
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 |
|---|---|
| get_itineraryA | Read the current itinerary for a trip: the place, how many days, and every activity already planned, grouped by day. Call this first. |
| add_activityA | Add one activity to a specific day of the trip. |
| remove_activityA | Remove an activity by its id. Ids are shown in square brackets by get_itinerary. |
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
Each tool has a clearly distinct purpose: reading the itinerary, adding an activity, and removing an activity. There is no overlap or ambiguity between them.
All tool names follow the same verb_noun pattern with snake_case: get_itinerary, add_activity, remove_activity. This is fully consistent and predictable.
Three tools is well-scoped for a simple trip planner. Each tool earns its place, and the count is neither too thin nor excessive for the apparent purpose.
The set covers the core lifecycle of reading, adding, and removing activities. The only minor gap is the lack of an update operation, but this can be worked around with remove_activity followed by add_activity.