Skip to main content
Glama

Vuelo support request status

get_support_ticket
Read-onlyIdempotent

Where a request to Vuelo's support team stands: with the team, replied (the reply is in the traveller's email), or resolved. Pass the ticket reference (SUP-...) and either the taskId of the booking in this conversation or the email the traveller gave. Use it when the traveller asks for an update. To add to a request, call contact_support again with the same booking and reason: it joins the same conversation.

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": {
      "ticket": "<ticket>"
    },
    "name": "get_support_ticket"
  }
}

Input Schema

NameRequiredDescriptionDefault
emailNoThe email the traveller gave for the reply.
mobileNoOr the mobile on the request.
taskIdNoThe booking's taskId, if it was made in this conversation.
ticketYesThe ticket reference, SUP-...

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / mobile
      Added value: +{
      +  "description": "Or the mobile on the request.",
      +  "maxLength": 30,
      +  "type": "string"
      +}
  2. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, not open-world), so the description's job is context — and it delivers: "replied" means the reply lives in the traveller's email, not in the response, which prevents an agent from claiming it has the answer text. It also discloses that lookups require both a ticket reference and a caller-supplied identity anchor.

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 tight sentences, front-loaded with the resource and its states before the invocation guidance. Slightly dense in the middle clause ("Pass the ticket reference (SUP-...) and either the taskId ... or the email"), but no filler.

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?

With four params, one required, no output schema, and full annotation coverage, the description supplies what is missing: the meaning of each status and the fact that the reply body is not returned. It stops short of saying what else the response contains (ticket age, assignment), but an agent can call 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 coverage is 100%, so per-parameter meanings are already documented and the baseline is 3. The description does add one thing the schema does not: that taskId and email are alternatives for verifying the caller, not both required — worth something, but the schema still carries most of the weight.

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?

Specific verb and resource (fetch the status of a Vuelo support ticket) with the possible states enumerated: with the team, replied, resolved. It reads clearly against contact_support, but the very similarly-named sibling follow_up_ticket is never mentioned, so the agent must still guess how those two differ.

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?

Explicit trigger ("Use it when the traveller asks for an update") and an explicit alternative path for the adjacent intent ("To add to a request, call contact_support again with the same booking and reason: it joins the same conversation"). No exclusion against follow_up_ticket, which is the one ambiguous neighbour.

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