Skip to main content
Glama
negm17111995

MAQAMI Travel

by negm17111995
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Cancel flight booking

post_flights_bookings_bookingid_cancellations
Destructive

Cancel a confirmed flight booking by submitting the booking ID and booking email. Verify the refund estimate first, then confirm to process the cancellation.

Instructions

Cancel a confirmed flight booking. First show the customer the refund estimate from get_flights_bookings_bookingid_cancellations and wait for a clear yes.

Requires the bookingId and the email used to book: the server only returns or changes a booking when they match.

Input Schema

NameRequiredDescriptionDefault
emailYesThe email address used to make the booking. The server checks it against the booking before returning or changing anything.
lastNameNoThe booking holder's last name, if the customer gives it. Optional.
bookingIdYesThe flight booking identifier to cancel

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv1.0.6
    • changedInput schema / properties / bookingId / description
      Previous value: -"The unique booking identifier"New value: +"The flight booking identifier to cancel"
    • addedInput schema / properties / email
      Added value: +{
+  "description": "The email address used to make the booking. The server checks it against the booking before returning or changing anything.",
+  "type": "string"
+}
    • addedInput schema / properties / lastName
      Added value: +{
+  "description": "The booking holder's last name, if the customer gives it. Optional.",
+  "type": "string"
+}
    • changedInput schema / required
      Previous value: -[
-  "bookingId"
-]New value: +[
+  "bookingId",
+  "email"
+]
  2. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=false, so the safety profile is covered; the description adds the crucial behavioral constraint that the server only acts when bookingId and email match. It stops short of describing post-cancellation state or refund timing, keeping it below 5.

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

Conciseness5/5

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

Two short sentences: the action first, then the mandatory pre-step, then the credential constraint. No filler, and the most important gating information is front-loaded.

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 no output schema, the description adequately covers the action, the required confirmation prerequisite, and auth matching. It could say what a successful cancellation returns or whether it is reversible, but for a destructive mutation whose annotations already flag destructiveness, this is close to complete.

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%, so each parameter including the optional lastName is already documented. The description reiterates the two required params and the match requirement but adds no syntax or format detail beyond the schema — baseline 3 applies.

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 ('Cancel a confirmed flight booking'), and the scoping word 'flight' distinguishes it from siblings like cancel_hotel_booking and cancelExperienceBooking without needing to open their schemas.

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?

Explicitly prescribes a workflow: first surface the refund estimate from `get_flights_bookings_bookingid_cancellations` and wait for a clear yes before cancelling. It names the sibling tool and the gating condition, leaving nothing to inference.

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

Deploy Server

Other Tools