Wisnu MCP
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 |
|---|---|
| tasks | {
"list": {},
"cancel": {},
"requests": {
"tools": {
"call": {}
},
"prompts": {
"get": {}
},
"resources": {
"read": {}
}
}
} |
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_flightsB | Search for available flights between two locations. Args: origin: Origin airport code (e.g., "JFK", "LAX") destination: Destination airport code (e.g., "LHR", "CDG") departure_date: Departure date in YYYY-MM-DD format return_date: Optional return date in YYYY-MM-DD format for round trips passengers: Number of passengers (default: 1) cabin_class: Cabin class preference Returns: Dictionary with flight search results |
| search_hotelsA | Search for available hotels in a location. Args: location: City or location name (e.g., "Paris", "New York") checkin_date: Check-in date in YYYY-MM-DD format checkout_date: Check-out date in YYYY-MM-DD format guests: Number of guests (default: 1) rooms: Number of rooms needed (default: 1) min_rating: Minimum hotel rating (0-5, optional) Returns: Dictionary with hotel search results |
| search_destinationsB | Get destination recommendations based on interests and preferences. Args: interests: List of interests (e.g., ["beach", "culture", "adventure", "food"]) budget_range: Budget category season: Preferred travel season Returns: Dictionary with destination recommendations |
| calculate_trip_costB | Calculate total estimated trip cost. Args: flight_cost: Cost of flights per person hotel_cost_per_night: Hotel cost per night num_nights: Number of nights daily_expenses: Estimated daily expenses per person (default: $100) num_travelers: Number of travelers (default: 1) Returns: Dictionary with cost breakdown |
| get_travel_tipsC | Get travel tips and recommendations for a destination. Args: destination: Destination city or country trip_type: Type of trip Returns: Dictionary with travel tips |
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
Each tool has a clearly distinct purpose with no overlap: calculate_trip_cost handles cost estimation, get_travel_tips provides destination advice, search_destinations recommends places based on preferences, search_flights finds flights, and search_hotels finds accommodations. The descriptions reinforce these unique functions, making misselection unlikely.
All tool names follow a consistent verb_noun pattern with snake_case: calculate_trip_cost, get_travel_tips, search_destinations, search_flights, and search_hotels. This uniformity makes the set predictable and easy to understand, with no deviations in style or convention.
With 5 tools, this server is well-scoped for travel planning, covering key aspects like cost calculation, destination recommendations, tips, flights, and hotels. Each tool earns its place without feeling excessive or insufficient for the domain.
The tool set covers core travel planning workflows: search (destinations, flights, hotels), cost estimation, and tips. Minor gaps exist, such as no booking or reservation tools, but agents can work around this by using search results for manual follow-up, and the surface supports most agent-driven planning tasks effectively.