Skip to main content
Glama

trivago_trivago-accommodation-radius-search

[trivago] Search live hotel and accommodation listings near specific coordinates — a landmark, address, venue, or neighborhood — aggregated via trivago's metasearch of major booking sites. Returns the same, filterable results as trivago-accommodation-search. Use when the user anchors their search to a place rather than a named destination (e.g. "near the stadium," "within walking distance of X").

Additional Information: {"knownInformation":{"currentYear":"2026","today":"2026-09-01"}}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
roomsNo The number of rooms, Number of rooms must be lower than or equal to the number of adults
adultsNo The number of adults.
arrivalYes The arrival date in YYYY-MM-DD format, today is 2026-09-01. The arrival date MUST be before the departure date. If the arrival date is not in the future, notify the user that the arrival date is not in the future.
countryNoISO alpha-2 country code that determines market-specific pricing and content. Default: US.US
filtersNo The filters that you want to apply to the search. Set true or false for each filter. Multiple filters can be selected.
childrenNo The number of children.
currencyNoISO 4217 currency code used to display prices. Default: USD.USD
languageNoLanguage code for translated content (e.g. EN_US, DE_DE, ZH_HANS_CN). Default: EN_US.EN_US
latitudeYesLatitude of the search target location (landmark, address, or neighborhood — not the user's location).
departureYes The departure date in YYYY-MM-DD format, today is 2026-09-01. The departure date MUST be after the arrival date. If the departure date is not after the arrival date, notify the user that the departure date is not after the arrival date.
longitudeYesLongitude of the search target location (landmark, address, or neighborhood — not the user's location).
hotel_ratingNo The hotel rating that you want to filter by. Set true or false for each rating. Multiple ratings can be selected.
children_agesNo Dashed separated list of children ages, e.g. 10-12-14
review_ratingNo The guest review rating that you want to filter by. Set true or false for each rating. Multiple ratings can be selected.

TDQS

A4.2/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations available, the description carries the behavioral burden. It does disclose that the search is 'live', aggregated via trivago's metasearch, and returns 'filterable results' identical to the sibling tool. However, it does not mention response format, possible limitations, or any other side effects. For a read-only search tool, this is adequate but not rich.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is compact and front-loaded, immediately stating the core function, then adding differentiation and usage guidance. Every sentence earns its place with no filler or redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (14 parameters, nested filter objects) the description leverages the 100% schema coverage well and adds the essential use-case distinction and sibling comparison. It could note the absence of a radius parameter or clarify the meaning of 'radius search' in the tool name, but overall an agent has enough to invoke it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema already explains all parameters. The description adds conceptual context for the coordinate parameters by framing them as landmarks/addresses/venues/neighborhoods, but this largely echoes the existing latitude/longitude parameter descriptions. No extra parameter meaning beyond the schema is provided.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb ('Search') and resource ('live hotel and accommodation listings near specific coordinates'), and clarifies the search target as a landmark, address, venue, or neighborhood. It explicitly differentiates itself from the sibling trivago-accommodation-search by positioning this tool for coordinate-anchored rather than named-destination searches.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly states when to use this tool ('when the user anchors their search to a place rather than a named destination') and provides concrete examples like 'near the stadium' and 'within walking distance of X'. It also points to trivago-accommodation-search as the alternative, giving clear routing guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

B3.2/5.0
Disambiguation3/5

Most tools are namespaced by vendor and resource, so ferry, tour, flight, hotel, and experience searches are broadly distinguishable. However, hotel search exists in both skiplagged and trivago, ferryhopper_search_trips is a deprecated duplicate of search_trips_v2, and several skiplagged calendar/anywhere tools overlap in flight-price discovery, which can cause misselection.

Naming Consistency2/5

Naming conventions are mixed across the set: plain underscores (airports_search), vendor-prefixed underscores (ferryhopper_get_ports), redundant prefixes (skiplagged_sk_hotels_search, trivago_trivago-accommodation-search), and hyphenated sub-APIs (tourradar_b2b-tour-details, tourradar_vertex-tour-search). There is no consistent verb_noun pattern and at least one version-suffixed deprecated name.

Tool Count1/5

With 56 tools, the server falls into the extreme-mismatch count band. The breadth is partly explained by eight vendor integrations, but many lookups, near-duplicate searches, and deprecated tools could be consolidated or split into focused MCP servers.

Completeness4/5

The tool surface covers most of the travel-planning lifecycle: airports, airlines, visa rules, FCDO advice, flights, hotels, cars, ferries, experiences, and tours including search, details, and tour booking. The main gaps are that only tours have an actual booking flow and there is no update/cancel or post-booking management.