[tourradar] Use this when you need language IDs for filtering tours by guide language.
Returns a list of all supported languages with their IDs, codes, and names for use in tour search filters.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description must convey behavioral traits. It discloses that the tool returns a list with IDs, codes, and names, and implies the operation is read-only. However, it does not mention any additional behavior such as response format, pagination, or errors, but for a simple list endpoint this is adequate.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is two sentences: the first states when to use the tool, the second states its output. Every word is purposeful, with no redundancy or filler. It is front-loaded with the tool's key purpose.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The tool is simple: no parameters, no output schema, and a straightforward listing purpose. The description fully explains why you would use it (to get language IDs for filtering) and what it returns (IDs, codes, names). This is complete given the tool's low complexity.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool has zero parameters, so the baseline is 4. The description does not need to add parameter semantics, and the schema already confirms no parameters exist. The description adds no parameter information because none is needed.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool returns a list of all supported languages with their IDs, codes, and names. It uses a specific verb ('Returns a list') and a specific resource ('supported languages'), and its purpose—supporting tour search filters—is unambiguous. It is clearly distinguished from sibling list tools by focusing on languages.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description explicitly says 'Use this when you need language IDs for filtering tours by guide language,' giving a clear use case. It does not mention when not to use it or alternatives, but the context is sufficient for a simple lookup tool.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
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 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.
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.
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.