Skip to main content
Glama

Buscar vuelos

search_flights
Read-onlyIdempotent

Search flights on WizTrip (the same search as wiz-trip.com/vuelos): one way or round trip, with adults, children and infants. origin and destination take an IATA code (city or airport: BUE, MVD, MIA) or a city name. Returns WizTrip's recommended flight, the cheapest and the shortest, plus more options, with selling prices in USD for the whole party, baggage, stops and schedule. The card shows them with a «Reservar ahora» button that opens the wiz-trip.com checkout of that flight. For a multi-city trip, or flight plus hotels, use trip_chat.

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": {
      "origin": "<origin>",
      "destination": "<destination>",
      "departure_date": "<departure_date>"
    },
    "name": "search_flights"
  }
}

Input Schema

NameRequiredDescriptionDefault
adultsNo
originYesIATA code or city name.
infantsNoUnder 2.
childrenNo2 to 11 years old.
cabin_classNo
destinationYesIATA code or city name.
return_dateNoYYYY-MM-DD, from today (2026-11-19) on. Omit for one way.
departure_dateYesYYYY-MM-DD, from today (2026-11-19) on.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / departure_date / description
      Previous value: -"YYYY-MM-DD, from today (2026-11-18) on."New value: +"YYYY-MM-DD, from today (2026-11-19) on."
    • changedInput schema / properties / return_date / description
      Previous value: -"YYYY-MM-DD, from today (2026-11-18) on. Omit for one way."New value: +"YYYY-MM-DD, from today (2026-11-19) on. Omit for one way."
  2. Changed2 schema fields changed
    • changedInput schema / properties / departure_date / description
      Previous value: -"YYYY-MM-DD, from today (2026-11-17) on."New value: +"YYYY-MM-DD, from today (2026-11-18) on."
    • changedInput schema / properties / return_date / description
      Previous value: -"YYYY-MM-DD, from today (2026-11-17) on. Omit for one way."New value: +"YYYY-MM-DD, from today (2026-11-18) on. Omit for one way."
  3. Changed2 schema fields changed
    • changedInput schema / properties / departure_date / description
      Previous value: -"YYYY-MM-DD, from today (2026-11-16) on."New value: +"YYYY-MM-DD, from today (2026-11-17) on."
    • changedInput schema / properties / return_date / description
      Previous value: -"YYYY-MM-DD, from today (2026-11-16) on. Omit for one way."New value: +"YYYY-MM-DD, from today (2026-11-17) on. Omit for one way."
  4. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered by structured data. The description does add real value beyond that by disclosing the response shape (recommended, cheapest, shortest, plus more options) and the downstream action (a «Reservar ahora» button opening the WizTrip checkout). It does not mention rate limits, pricing volatility, or result freshness, which are the notable open behaviors for a live fare search.

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?

Front-loaded with the core action and the site equivalence, then progressively adds return details and the routing hint. It is dense but each sentence carries information; the paragraph could be split for readability but nothing is padding.

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

Completeness5/5

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

With no output schema, the description carries the burden of explaining what comes back, and it does: recommended/cheapest/shortest options, USD prices for the whole party, baggage, stops, schedule, and the booking handoff. For an 8-parameter search tool that is complete enough to call 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 75%, so the baseline is 3. The description reinforces that origin/destination accept an IATA code or city name and clarifies that prices cover the whole party, which relates to the passenger parameters. It adds nothing about cabin_class, passenger age bands, or default values that the schema does not already state.

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?

States a specific verb and resource ("Search flights on WizTrip") and pins it to a concrete endpoint (wiz-trip.com/vuelos), then scopes the trip types (one way or round trip) and party composition. The flight resource is unambiguous against siblings like search_hotels or search_transfers.

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?

Gives an explicit exclusion with a named alternative: multi-city trips or flight-plus-hotel packages should go to trip_chat. One-way vs round-trip selection is implied by the return_date omission rule. It does not discuss other alternatives or when a user might prefer search_transfers/search_hotels, but the resource naming makes those obvious.

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