Gondola Award Travel Search

cancel_flight_booking

Destructive

Preview flight cancellation first with confirm=false or omitted. Show the returned itinerary cancellation scope and exact terms before asking the traveler to confirm. A void preview means Gondola will cancel the itinerary first and only then attempt ticket settlement; the amount returned is not known. To confirm, send the same booking_id plus the preview's cancellation_id, currency, expected_refund_amount, expected_ticket_settlement_method, and expected_ticket_settlement_affected_count with confirm=true, echoing only the terms present in the preview. When the preview has no verified refund amount, leave expected_refund_amount omitted. Itinerary cancellation, ticket settlement, refunds, customer payouts, credits, and Gondola Cash are separate states. If the outcome is uncertain, retrieve the booking or cancellation state instead of repeating the mutation.

Input Schema

TableJSON Schema

Name	Required	Description
`confirm`	No	Leave false or omit for the required preview. Set true only after the traveler accepts the exact preview terms.
`currency`	No	The exact currency from the preview. Required by the handler only when confirm=true.
`booking_id`	Yes	The Gondola flight booking ID to preview or cancel.
`cancellation_id`	No	The exact Gondola cancellation ID from the preview. Required by the handler only when confirm=true.
`expected_refund_amount`	No	The exact refund amount string from the preview. Required by the handler for confirmation when the preview includes an amount; omit it when the preview amount is unknown.
`expected_ticket_settlement_method`	No	The exact ticket settlement method from the preview. Echo void when the preview advertises ticket settlement; otherwise omit it.
`expected_ticket_settlement_affected_count`	No	The exact affected ticket-document count from the preview. Required with expected_ticket_settlement_method; otherwise omit it.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedSep 24, 2026

addedInput schema / properties / expected_ticket_settlement_affected_count

Added value: +{
+  "description": "The exact affected ticket-document count from the preview. Required with expected_ticket_settlement_method; otherwise omit it.",
+  "type": "integer"
+}

addedInput schema / properties / expected_ticket_settlement_method

Added value: +{
+  "description": "The exact ticket settlement method from the preview. Echo void when the preview advertises ticket settlement; otherwise omit it.",
+  "enum": [
+    "void"
+  ],
+  "type": "string"
+}

AddedSep 23, 2026

TDQS

A5/5.0

Behavior5/5

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

Beyond the destructiveHint annotation, the description discloses the risky void-preview behavior: Gondola cancels the itinerary first and only then attempts ticket settlement, with the returned amount unknown. It also clarifies that itinerary cancellation, ticket settlement, refunds, payouts, credits, and Gondola Cash are separate states, which materially changes how an agent should interpret results.

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?

The description is long but every sentence carries essential guidance: the preview-first rule, the confirm contract, omission rules, state separation, and the no-retry fallback. It is front-loaded with the most critical safety instruction and avoids repetition or filler.

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?

Given the tool's destructive, open-world nature and seven-parameter confirmation workflow, the description is complete: it defines preview/confirm behavior, exact echo requirements, unknown-refund handling, state separation, and when to stop mutating and read state instead. An output schema exists, so return-value explanation is not needed here.

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

Parameters5/5

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

Although the schema already documents all seven parameters at 100% coverage, the description adds the crucial two-phase semantics: which fields must be echoed on confirm, which must be omitted when absent from the preview, and the conditional requirement for expected_refund_amount. This is meaningful value beyond the input schema.

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?

The description states a precise workflow: preview a flight cancellation with confirm=false, then confirm with the echoed preview terms. It clearly distinguishes this flight-booking cancellation tool from vehicle cancellation and read-only booking tools by naming the resource and the two-phase mutation contract.

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?

It explicitly instructs to preview first, only confirm after the traveler accepts the exact terms, and never repeat the mutation when the outcome is uncertain. It also names the alternative—retrieve the booking or cancellation state—for uncertain situations, which is strong usage guidance.

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

All Gondola Award Travel Search tools Inspect

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.