Skip to main content
Glama
Sign In

MAQAMI Travel

by co.maqami.mcp
OverviewDiscussionsAdmin

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.

Error codes

Product-operation codes are listed below. Shared authentication/access/rate-limit middleware can return common codes such as 401, 40301 or 4290. HTTP status and error code are separate; do not parse message text.

Code

Meaning

75001

booking not found

75002

this booking has already been cancelled

75003

cancellation is not allowed for this booking

75004

the activity has already started

75005

invalid cancellation preview request

75006

cancellation preview provider request failed

75007

cancellation preview provider request timed out

75008

cancellation preview request is unauthorized

75009

cancellation preview request is forbidden

75010

cancellation preview service is temporarily unavailable

75099

failed to retrieve cancellation preview

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.
bookingIdYesMAQAMI experience booking ID from the booking confirmation

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • 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. Changed1 schema field changed
    • 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"
  3. Added
  4. Removed
  5. Added

TDQS

A4.8/5.0
Behavior5/5

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

Beyond the annotations (readOnly, non-destructive, idempotent), the description discloses the ownership/verification requirement ('the server only returns or changes a booking when they match'), explicit non-mutation semantics, a full product-operation error-code table with meanings, and a note that shared middleware may return 401/40301/4290 and that message text must not be parsed. That is substantial extra behavioral context.

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?

Well structured and front-loaded: Overview, When to Use, What You Get, Quick Start, then error codes. The 12-row error table is long but scannable and actionable; the only cost is overall length relative to what an agent must read before acting.

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?

No output schema exists, and the 'What You Get' section enumerates the return shape (cancellable, policy with cancellationFee, refundAmount, refundType, estimateConfidence, currency, sellingPrice). Combined with error semantics and the identity requirement, nothing an agent needs to call or interpret this tool is missing.

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 schema already documents all three parameters; the description nonetheless reinforces the critical pairing semantics that bookingId and the booking email must match before anything is returned. It does not add format/syntax detail beyond the schema, so it earns a 4 rather than a 5.

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 Overview states a specific verb and resource: preview the refund amount and cancellation fee for a booking without committing to cancellation. It also explicitly names the sibling it is not (cancelExperienceBooking) and the sibling it relates to (POST /experiences/bookings for the bookingId), so an agent can route correctly without opening a 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?

A dedicated 'When to Use' section names two concrete scenarios (cancellation confirmation screens, support tooling) and the Quick Start explicitly disambiguates: 'This does not cancel the booking - cancelExperienceBooking cancels it.' Both inclusion and exclusion conditions are stated.

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

All MAQAMI Travel toolsInspect
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.

Resources