Skip to main content
Glama

Event Escapes

by com.eventescapes
OverviewDiscussionsAdmin

create_payment_link

THE way to book with Event Escapes. Works exactly like our WhatsApp bookings: you (the agent) give us the customer's details and the exact items, we lock LIVE prices in a cart and return a SECURE STRIPE PAYMENT URL for that exact total, which the customer pays. Before calling, collect from the customer and pass: (1) customer_email, confirmed letter-perfect; (2) customer_first_name and customer_last_name of the lead traveller; (3) customer_consent, the customer's own words asking you to book these items; (4) items: for a hotel the hotel_id from search_hotels_near_event with check_in, check_out and adults; for tickets the event_id from search_events with quantity; for an experience the activity_code from search_experiences with activity_date (experiences currently come back as a secure site link for the customer to complete, hotels and tickets are booked here). Never invent dates, guest counts or emails. If the result status is action_required, read the message, collect what it asks for (a ticket category, a price change to confirm, or for SOME SE365 tickets per-attendee passport or date of birth, which the tool names exactly), and call again with the same items plus the extra fields. Items accumulate in that customer's cart for 90 minutes across calls, and the payment URL covers everything in it, so a second call with a new item returns one link for the whole trip. Nothing is charged until the customer pays the URL, and the card is only captured once every booking is confirmed. Event Escapes is the merchant of record. The payment URL expires in about 30 minutes.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
itemsYesWhat to book, in order. Each item is one hotel room, one ticket line, or one experience.
promo_codeNoPromo code only if the customer gave one, exactly as typed.
attendee_namesNoEVENT tickets for more than one attendee: comma-separated full names. The tool tells you if needed.
customer_emailYesCustomer's email, confirmed back to them letter-perfect. Receipt and confirmations go here.
customer_phoneNoCustomer's mobile in E.164 (+61..., +1...), if known.
accept_new_priceNotrue only after the tool reported a price change AND the customer agreed to the new total.
attendee_detailsNoOnly when the tool asks: one entry per attendee separated by ';', e.g. 'name=John Smith, dob=1985-03-04, passport=N1234567, nationality=Australia'. Include only the fields the tool asked for.
customer_consentYesREQUIRED. The customer's own words asking you to book these items (e.g. 'yes book the Marriott and 2 tickets').
residency_countryNoCustomer's country of residence, if stated (hotel prices vary by residency).
customer_last_nameYesLead traveller's last name.
customer_first_nameYesLead traveller's first name.
details_confirm_quoteNoRequired when attendee_details carries passport or date of birth: the customer's confirmation after you read the details back and warned they cannot be changed.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior5/5

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

Beyond annotations (readOnlyHint=false, destructiveHint=false), the description discloses rich behaviors: the cart accumulates across calls for 90 minutes, the payment URL expires in about 30 minutes, nothing is charged until the customer pays, card capture happens only after confirmation, and Event Escapes is merchant of record. It also explains the action_required retry flow and special SE365 passport/DOB requirements, adding substantial operational 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?

The description is long and dense, but nearly every sentence carries operational information: booking flow, required input order, action_required retry, cart accumulation, expiry, and payment behavior. It avoids filler, though a more structured layout (separating prerequisites, retry logic, and constraints) would improve scannability.

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 complex tool with 12 parameters, 5 required, no output schema, and a multi-call workflow, the description covers everything an agent needs: prerequisite data collection, item type-specific source IDs, retry behavior with the 'result status' signal, cart persistence, URL expiry, and payment capture semantics. It compensates fully for the absent output schema.

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 schema coverage is 100%, the description adds meaningful semantics: customer_consent must be the customer's own words, IDs must come from specific sibling tools (e.g., hotel_id from search_hotels_near_event), dates and counts must never be invented, and accept_new_price should only be true after a tool-reported price change and customer agreement. This goes well beyond the schema's field descriptions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description identifies a specific verb+resource: it creates a payment link that books hotels, events, and experiences, framed as 'THE way to book with Event Escapes.' It clearly states the tool's role and output (a Stripe payment URL), but does not explicitly name sibling tools or explain how they differ, so it stops just short of full sibling differentiation.

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 description gives explicit when-to-call guidance: collect customer details first, pass IDs from sibling search tools, call again if action_required, and account for the 90-minute cart window. It outlines the full booking procedure and prerequisites, though it does not explicitly state when not to use this tool versus build_event_link/build_package_link, so exclusions are implied rather than stated.

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

All Event Escapes 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