Skip to main content
Glama

Vuelo Travel

by com.getvuelo
OverviewDiscussionsAdmin

Send the traveller their booking page

find_my_booking

For a traveller who booked with Vuelo before, in another conversation, and wants to see, change, cancel or get help with it: Vuelo texts the booking's own page to the mobile on that booking. On that page they can cancel, add it to their calendar, and contact Vuelo's team. Pass their Vuelo booking reference (VU-...) and the email or mobile they booked with. If they do not have the reference, pass the mobile they booked with alone (with country if it is not written with +): Vuelo texts that number a link to each of its latest bookings. You never see a link or whether anything matched, so tell them: if the details match, Vuelo has texted the mobile on the booking. They can also see every booking on their mobile at Vuelo's bookings page (/bookings on the site their booking links open), with a code texted to it. Never search their email or messages for a reference instead: ask for the mobile. For anything else they want a person for, use contact_support.

Input Schema

NameRequiredDescriptionDefault
emailNoThe email the traveller booked with.
mobileNoThe mobile on the booking: with the reference instead of the email, or alone without the reference.
countryNoFor a mobile typed the local way (06 12 34 56 78), the country it is from, as an ISO code (FR). Not needed for a number with +.
referenceNoThe Vuelo booking reference, VU-... Leave out if the traveller does not have it, and pass the mobile alone.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / country
      Added value: +{
+  "description": "For a mobile typed the local way (06 12 34 56 78), the country it is from, as an ISO code (FR). Not needed for a number with +.",
+  "maxLength": 2,
+  "minLength": 2,
+  "type": "string"
+}
    • changedInput schema / properties / mobile / description
      Previous value: -"Or the mobile on the booking, instead of the email."New value: +"The mobile on the booking: with the reference instead of the email, or alone without the reference."
    • changedInput schema / properties / reference / description
      Previous value: -"The Vuelo booking reference, VU-..."New value: +"The Vuelo booking reference, VU-... Leave out if the traveller does not have it, and pass the mobile alone."
    • removedInput schema / required
      Removed value: -[
-  "reference"
-]
  2. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Goes well beyond the annotations by disclosing the critical invisible outcome: 'You never see a link or whether anything matched', plus the exact wording to relay to the traveller. Also explains the downstream page capabilities and the alternative self-service route at /bookings. Sending an SMS is consistent with readOnlyHint=false and openWorldHint=true; no contradiction.

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 traveller scenario before the mechanics, and every sentence is load-bearing on routing or behaviour. Slightly overlong: the enumeration of what the page offers ('cancel, add it to their calendar, contact Vuelo's team') is nice-to-have context rather than decision-relevant.

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?

No output schema exists, and the description explicitly fills that gap by telling the agent it receives no link and no match confirmation, plus what to say instead. Combined with the fallback path and the /bookings self-service option, nothing an agent needs to call this correctly is missing.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds real value the schema cannot express: the OR-combination rules (reference + email or mobile; mobile alone when no reference; country only for locally-typed numbers). The schema descriptions already restate much of this, so the gain is incremental rather than transformative.

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?

States a specific verb+resource: Vuelo texts the booking's own page link to the mobile on the booking, plus what the traveller can do on that page. An agent can distinguish it from get_booking or cancel_booking. It does not explicitly contrast with resend_link, the nearest sibling, so it falls short of full sibling differentiation.

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?

Gives an explicit triggering scenario (traveller who booked before, in another conversation, wanting to see/change/cancel/get help), two concrete invocation paths (reference+email/mobile, or mobile alone), a negative instruction ('Never search their email or messages for a reference instead: ask for the mobile'), and an alternative ('use contact_support').

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

All Vuelo Travel toolsInspect
Try in Browser
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

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources