Skip to main content
Glama

Get flight cancellation link

post_flights_bookings_bookingid_cancellations
Read-onlyIdempotent

Flight bookings are cancelled on MAQAMI's website, not in this chat. When a customer wants to cancel a flight, give them https://book.maqami.co/manage-bookings and tell them to continue from there: choose "Flight reservations", enter the last name and the booking ID, then follow the steps to see the refund and cancel. Calling this tool returns the same link and steps.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "post_flights_bookings_bookingid_cancellations"
  }
}

Input Schema

NameRequiredDescriptionDefault
bookingIdNoOptional: the flight booking ID, if the customer gave it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • changedInput schema / properties / bookingId / description
      Previous value: -"The flight booking identifier to cancel"New value: +"Optional: the flight booking ID, if the customer gave it."
    • removedInput schema / properties / email
      Removed value: -{
      -  "description": "The email address used to make the booking. The server checks it against the booking before returning or changing anything.",
      -  "type": "string"
      -}
    • removedInput schema / properties / lastName
      Removed value: -{
      -  "description": "The booking holder's last name, if the customer gives it. Optional.",
      -  "type": "string"
      -}
    • removedInput schema / required
      Removed value: -[
      -  "bookingId",
      -  "email"
      -]
  2. Changed2 schema fields changed
    • changedInput schema / properties / email / description
      Previous value: -"The passenger contact email (required for verification)."New value: +"The email address used to make the booking. The server checks it against the booking before returning or changing anything."
    • changedInput schema / properties / lastName / description
      Previous value: -"The passenger last name (optional alternative for verification)."New value: +"The booking holder's last name, if the customer gives it. Optional."
  3. 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 readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is covered. The description adds genuinely useful behaviour beyond that: nothing is mutated, the result is a fixed link plus step-by-step instructions, and the actual cancellation happens on an external site (openWorldHint). It stops short of saying how the optional bookingId changes the output or whether the link is personalised when an ID is supplied.

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?

The description is front-loaded with the key constraint (cancellation happens off-chat) and then the exact URL and steps, all of which are operationally necessary for the agent's reply. There is mild redundancy between "tell them to continue from there" and "Calling this tool returns the same link and steps", 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 one optional parameter, no output schema and read-only annotations, the description supplies everything needed to call the tool correctly and to relay the result to the customer. The only gap is the side effect of supplying bookingId and how this tool relates to get_flights_bookings_bookingid_cancellations, both of which are minor for a link-returning helper.

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 100% and the single parameter (bookingId) is documented as optional in the schema itself. The description never mentions bookingId, so it adds no semantics such as whether passing it deep-links the customer to the right reservation or merely echoes the same generic URL. Baseline 3 applies when the schema does the 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?

The description makes it explicit that despite the POST-style name, this tool does not cancel anything: "Calling this tool returns the same link and steps." That is a specific, actionable statement of what the tool yields (a deep link plus instructions) and it implicitly separates it from cancel_hotel_booking / cancelExperienceBooking, which the text says are not how flights are handled. It does not, however, distinguish this tool from the same-suffixed sibling get_flights_bookings_bookingid_cancellations, so an agent still has to infer that distinction from naming alone.

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?

"When a customer wants to cancel a flight, give them https://book.maqami.co/manage-bookings" gives a clear triggering condition and even prescribes the agent's response behaviour. It effectively excludes doing the cancellation in chat, which is strong when-not guidance. What is missing is any pointer to alternatives or complements, e.g. checking get_flights_bookings_bookingid_cancellations for existing cancellations or get_flights_bookings_bookingid for booking details first.

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.