Skip to main content
Glama
negm17111995

MAQAMI Travel

by negm17111995
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

prebookExperienceTour

Create a temporary hold on a selected tour slot and a Stripe PaymentIntent, returning transactionId and secretKey so checkout can confirm payment before booking.

Instructions

Overview

Create a temporary hold on the selected tour slot and a Stripe PaymentIntent for checkout.

When to Use

  • Checkout start — After the user picks option, slot, and participants from booking-options

  • Payment setup — Obtain transactionId and secretKey for Stripe SDK confirmation

  • Hold window — Reserve inventory for ~10 minutes before book

What You Get

  • Checkout context — tourId, optionId, dateTime, language, participants, and pricing echoed back

  • Provider refs — cartId, experienceBookingId, providerBookingId, status, reservationExpiresAt

  • Stripe fields — transactionId, secretKey, paymentTypes: ["TRANSACTION_ID"]

Quick Start

POST the same selection used for display pricing from booking-options with usePaymentSdk: true. Confirm payment with Stripe, then call POST /experiences/bookings.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
paymentNoOptional Stripe metadata (e.g. statement descriptor suffix).
currencyYesISO 4217 currency code used for validate and downstream book cart.
languageYesISO language code used for validate and downstream book cart.
selectionYes
usePaymentSdkYesPhase 1 requires `true` to create a Stripe PaymentIntent.
clientReferenceIdNoPartner reference echoed in prebook response and stored on the checkout session.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior5/5

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

With annotations already covering mutation/safety profile, the description adds meaningful behavior: a temporary inventory hold of about 10 minutes, creation of a Stripe PaymentIntent, and the returned provider and Stripe references. This goes well beyond the structured hints.

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 markdown structure is front-loaded with Overview, When to Use, What You Get, and Quick Start. Despite its length, every section serves a distinct purpose for a complex checkout-preparation tool.

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?

For a nested-schema tool with no output schema, the description supplies the missing return context, the Stripe flow, and the next step after confirmation. It is complete enough for correct invocation and sequencing.

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 already 83%, so the schema carries most parameter meaning. The description adds only light context, mainly that the selection should match what was used for display pricing and that usePaymentSdk must be true, which is already documented in the 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 specific verb and resource: 'Create a temporary hold on the selected tour slot and a Stripe PaymentIntent for checkout.' It clearly distinguishes this prebook/hold operation from the final booking step referenced later.

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?

The 'When to Use' section gives clear triggering conditions (after booking-options selection, for payment setup, within the hold window) and the Quick Start sequences the next call. It lacks explicit when-not-to-use guidance or named sibling alternatives, but the context is strong.

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