Skip to main content
Glama
hhw67865

TripAdvisor Vacation Planner MCP Server

by hhw67865
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

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

Server capabilities have not been inspected yet.

Tools

Functions exposed to the LLM to take actions

NameDescription
search_locationsB
Search for locations on TripAdvisor

Args:
    query: Search term (e.g., "hotels in Paris")
    category: Optional category filter (e.g., "hotels", "restaurants", "attractions")
get_nearby_locationsB
Find locations near a specific latitude and longitude

Args:
    latitude: Latitude coordinate
    longitude: Longitude coordinate
    category: Optional category filter (e.g., "hotels", "restaurants", "attractions")
get_location_details_toolB
Get essential details about a location by ID for trip planning

Args:
    location_id: TripAdvisor location ID
plan_vacationB
Initiates the vacation planning process using the structured prompt.
This should be used whenever a user wants to plan a trip or vacation.

Returns:
    A message confirming the vacation planning process has started

Prompts

Interactive templates invoked by user choice

NameDescription
vacation_plannerCreate an interactive prompt for planning a personalized vacation

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

B3.1/5.0

Scored across 4 tools

Disambiguation4/5

The tools have mostly distinct purposes: get_location_details_tool retrieves specific location info, get_nearby_locations finds nearby places, search_locations searches by query, and plan_vacation initiates trip planning. However, get_nearby_locations and search_locations could potentially overlap if a user searches for 'hotels near me' versus using coordinates, but their descriptions clarify the distinction.

Naming Consistency3/5

The naming is mixed: get_location_details_tool, get_nearby_locations, and search_locations follow a verb_noun pattern, but plan_vacation uses a verb_noun without 'get' or 'search', and get_location_details_tool includes '_tool' suffix inconsistently. This creates a readable but not fully consistent convention across all tools.

Tool Count3/5

With 4 tools, the count is borderline for a vacation planner server. It covers basic functions like searching and planning, but feels thin for a comprehensive trip planning domain, potentially lacking tools for booking, reviews, or itinerary management, which might limit agent effectiveness.

Completeness2/5

The tool surface has significant gaps for a vacation planner. It includes search and planning initiation but lacks CRUD operations for itineraries, booking tools, review access, or update/delete functions for planned trips. This incompleteness will likely cause agent failures in handling full vacation planning workflows.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources