Travel MCP Server
Server 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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_weatherB | Returns the current weather for a city. |
| get_current_date_toolA | Returns today's date in a human-readable format. |
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 2 tools
The two tools are completely distinct: one returns the current date, the other returns weather for a city. There is no overlap in their purposes.
Both tools use the 'get_' prefix, but one includes a redundant '_tool' suffix. Otherwise, naming patterns are consistent (verb_noun).
With only 2 tools, the server is very thin for a travel domain. Typical travel services would require many more tools (e.g., flights, hotels, destinations).
The tool surface is severely incomplete for a travel server. Essential operations like searching destinations, booking flights, or getting hotel info are missing.