Skip to main content
Glama

Buscar traslados

search_transfers
Read-onlyIdempotent

Search airport transfers on WizTrip (Hotelbeds): private and shared, from an airport (airport, IATA) to a hotel (hotel, its name) when the flight lands (arrival), and back to the airport when the return flight leaves (departure, optional). Prices are WizTrip selling prices in USD for the whole vehicle or service (not per person), round trip when departure is given. Transfers are not sold alone on wiz-trip.com: they are added when booking a flight, hotel or flight + hotel there.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "airport": "<airport>",
      "hotel": "<hotel>",
      "arrival": "<arrival>",
      "ages": "<ages>"
    },
    "name": "search_transfers"
  }
}

Input Schema

NameRequiredDescriptionDefault
agesYesAge of every traveller, e.g. [35, 33, 8]. At least one adult (18+).
hotelYesHotel name, e.g. "Copacabana Palace".
airportYesIATA code of the airport, e.g. "GIG".
arrivalYesYYYY-MM-DDTHH:mm, local time the flight lands, from today (2026-11-19) on.
departureNoYYYY-MM-DDTHH:mm, local time the return flight takes off. Optional.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / arrival / description
      Previous value: -"YYYY-MM-DDTHH:mm, local time the flight lands, from today (2026-11-18) on."New value: +"YYYY-MM-DDTHH:mm, local time the flight lands, from today (2026-11-19) on."
  2. Changed1 schema field changed
    • changedInput schema / properties / arrival / description
      Previous value: -"YYYY-MM-DDTHH:mm, local time the flight lands, from today (2026-11-17) on."New value: +"YYYY-MM-DDTHH:mm, local time the flight lands, from today (2026-11-18) on."
  3. Changed1 schema field changed
    • changedInput schema / properties / arrival / description
      Previous value: -"YYYY-MM-DDTHH:mm, local time the flight lands, from today (2026-11-16) on."New value: +"YYYY-MM-DDTHH:mm, local time the flight lands, from today (2026-11-17) on."
  4. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the bar is lower; the description still adds genuinely new behavior: prices are WizTrip selling prices in USD for the whole vehicle/service rather than per person, and the search becomes round trip when `departure` is supplied. It does not describe result ordering, availability semantics, or whether an empty result is possible.

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

Conciseness4/5

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

Three sentences, front-loaded with the resource and scope, then the parameters, then the commercial caveat. Sentence 2 is dense but every clause carries information; the final restriction sentence is non-obvious and earns its place.

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?

For a five-parameter, fully documented read-only search with no output schema, the description supplies the missing concepts an agent needs: directionality of the trip, whole-vehicle USD pricing, and the round-trip trigger. It could go slightly further on what a result set contains (transfer options, providers, pickup details), but nothing essential is missing to call the tool 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 coverage is 100%, so all five parameters already carry descriptions with formats and examples. The description reinforces the roles of airport (IATA), hotel (name), arrival, and optional departure, but adds little syntax or constraint detail beyond the schema; baseline 3 applies since the schema does the documentation work.

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

Purpose4/5

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

"Search airport transfers on WizTrip (Hotelbeds): private and shared" gives a specific verb plus resource and adds the directional model (airport→hotel on arrival, hotel→airport on departure). The transfer resource is clearly distinct from the flight/hotel/activity siblings, though no sibling is named explicitly to redirect an agent.

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

Usage Guidelines4/5

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

The description sets a clear usage context: airport transfers only, tied to a flight arrival and optionally a return departure. The closing sentence adds an important commercial constraint (transfers are not sold standalone on wiz-trip.com, they attach to a flight/hotel booking), which tells the agent when this result can actually be booked, but no explicit when-not-to-use or alternative tool is named.

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.

Resources