Skip to main content
Glama

book_slot

Book last-minute tour or activity slots with two payment options: generate Stripe checkout URLs for customer payment or use pre-funded wallets for automated booking.

Instructions

Book a last-minute slot for a customer. Two modes:

APPROVAL MODE (default — no wallet_id):
    Creates a Stripe Checkout Session and returns a checkout_url.
    You MUST share this URL with the customer immediately — do not summarise it,
    do not wait, show it directly so they can complete payment.
    The booking is confirmed with the supplier after payment succeeds.
    The session expires in 24 hours.

AUTONOMOUS MODE (wallet_id + execution_mode='autonomous'):
    The booking completes immediately using a pre-funded agent wallet.
    Returns a confirmation_number directly — no checkout step, no human action needed.
    Use this when your application manages payment on behalf of the customer.

Args:
    slot_id:        Slot ID from search_slots results.
    customer_name:  Full name of the person attending.
    customer_email: Email address for booking confirmation.
    customer_phone: Phone number including country code (e.g. +15550001234).
    quantity:       Number of people (default 1). Price is per-person × quantity.
    wallet_id:      Pre-funded agent wallet ID (format: wlt_...). Enables autonomous mode.
    execution_mode: Set to 'autonomous' when providing a wallet_id.

Returns:
    Approval mode:   { success: true, checkout_url, booking_id, expires_at, action_required }
    Autonomous mode: { success: true, confirmation_number, booking_id, status: 'booked' }
    On error:        { success: false, error }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
slot_idYes
customer_nameYes
customer_emailYes
customer_phoneYes
quantityNo
wallet_idNo
execution_modeNo
Behavior4/5

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

With no annotations provided, the description carries full burden and does an excellent job disclosing behavioral traits: it explains the two distinct modes, payment flow differences (Stripe Checkout vs. pre-funded wallet), session expiration (24 hours), and immediate action requirements (sharing URL directly). It doesn't cover rate limits or error handling specifics, but provides 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-structured with clear sectioning (two modes, args, returns), uses bullet points for readability, and every sentence earns its place by providing essential operational guidance. It's appropriately sized for a complex tool with multiple modes and avoids redundancy.

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 complexity (7 parameters, two distinct modes, payment integration) and absence of both annotations and output schema, the description provides complete context: it explains both operational modes, documents all parameters, specifies return formats for both success cases and errors, and provides necessary implementation guidance. No significant gaps remain.

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?

With 0% schema description coverage, the description fully compensates by explaining all 7 parameters: it clarifies slot_id's source (search_slots results), provides format examples for customer_phone, explains quantity's effect on pricing, and crucially details the interaction between wallet_id and execution_mode that triggers autonomous mode. This adds significant meaning beyond the bare 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 clearly states the tool's purpose with specific verbs ('Book a last-minute slot for a customer') and distinguishes it from siblings by focusing on booking functionality rather than searching (search_slots), checking status (get_booking_status), or retrieving supplier info (get_supplier_info). The two operational modes further clarify the specific actions involved.

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 description provides explicit guidance on when to use each mode: approval mode (default, no wallet_id) for customer-facing payment flows, and autonomous mode (wallet_id + execution_mode='autonomous') for automated payment scenarios. It clearly distinguishes between the two alternatives and specifies the conditions for each.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/johnanleitner1-Coder/lastminutedeals-api'

If you have feedback or need assistance with the MCP directory API, please join our Discord server