MAQAMI Travel

by io.github.negm17111995

Overview Discussions Admin

Preview tour cancellation

getExperienceBookingCancelPreview

Read-onlyIdempotent

Overview

Preview the refund amount and cancellation fee for a booking before committing to cancel it.

When to Use

Cancellation confirmation screens - Show the guest exactly what they'll be refunded
Support tooling - Check whether a booking is still cancellable before offering a refund

What You Get

cancellable - Whether the booking can currently be cancelled
policy - cancellationFee, refundAmount, refundType, estimateConfidence, currency, sellingPrice

Quick Start

Use this with the bookingId from POST /experiences/bookings. This does not cancel the booking - cancelExperienceBooking cancels it.

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

Input Schema

Name	Required	Description
`email`	Yes	The email address used to make the booking. The server checks it against the booking before returning or changing anything.
`lastName`	No	The booking holder's last name, if the customer gives it. Optional.
`bookingId`	Yes	MAQAMI experience booking ID from the booking confirmation

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 7, 2026

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"
+]

Changed1 schema field changedOct 6, 2026

changedInput schema / properties / bookingId / description

Previous value: -"Dispatcher booking ID returned from POST /experiences/bookings"New value: +"MAQAMI experience booking ID from the booking confirmation"

First observedOct 4, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and idempotentHint=true, so the safety profile is carried structurally. The description still adds real value beyond that: the booking is only returned when bookingId and email match, and it enumerates the returned policy fields. No rate limits or error behavior are described, so not a 5.

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 purpose and structured under clear headings, with no filler sentences. The section scaffolding is slightly heavier than needed for a three-parameter read tool, but nothing is redundant.

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?

With no output schema, the 'What You Get' section usefully enumerates cancellable and the policy fields. Prerequisites (bookingId + matching email), the non-mutating guarantee, and the cancelling alternative are all present, so an agent has everything needed to call it correctly.

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 meaning: it explains that bookingId comes from POST /experiences/bookings and that email must match the booking or the server refuses to return it. lastName is left to the schema, which is acceptable.

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 precise verb+resource: preview the refund amount and cancellation fee for a booking before committing. It explicitly names the sibling it is not ('This does not cancel the booking - cancelExperienceBooking cancels it'), so an agent can distinguish it without opening either schema.

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?

The 'When to Use' section gives two concrete scenarios (cancellation confirmation screens, support tooling), and the Quick Start excludes the destructive alternative by name. When, why, and what-not are all covered.

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

All MAQAMI Travel tools Inspect

Try in Browser