Skip to main content
Glama

hemmabo_booking_checkout

Create a booking and generate a Stripe checkout page for payment. Optionally pass a quote ID to lock the price.

Instructions

Create a booking with Stripe payment and return a checkout URL. Use this tool when the user is ready to pay — it creates the booking record and generates a Stripe payment page. Do NOT call twice for the same booking — check hemmabo_booking_status first to avoid double charges. Optionally pass quoteId from hemmabo_booking_negotiate to lock the price. Returns reservationId, paymentUrl (Stripe checkout page), and pricing details.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
propertyIdYesProperty UUID from hemmabo_search_properties (e.g. '550e8400-e29b-41d4-a716-446655440000').
checkInYesArrival date in ISO 8601 format (YYYY-MM-DD, e.g. '2026-07-15'). Must be today or later.
checkOutYesDeparture date in ISO 8601 format (YYYY-MM-DD, e.g. '2026-07-22'). Must be after checkIn.
guestsYesTotal number of guests as integer >= 1 (e.g. 4).
guestNameYesFull name of primary guest (e.g. 'Anna Svensson').
guestEmailYesEmail for booking confirmation (e.g. 'anna@example.com'). Must be a valid email address.
guestPhoneNoPhone with country code (e.g. '+46701234567'). Optional but recommended.
quoteIdNoQuote ID from hemmabo_booking_negotiate to lock the price. Optional — if omitted, a fresh federation price is calculated at checkout time.
paymentModeNo'checkout_session' (default): returns Stripe redirect URL. 'payment_intent': returns client_secret for programmatic payment (AI agent MPP flow).
channelNo'federation' (default): applies direct booking discount. 'public': uses standard website rate.
Behavior4/5

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

No annotations provided, so description carries full burden. It discloses booking creation, Stripe payment page generation, and the effect of quoteId. However, it omits details on idempotency, payment failure handling, and booking confirmation after payment.

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?

Four sentences, all essential and front-loaded. No unnecessary words or repetition. Efficient and clear.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Covers purpose, usage, parameters, and outputs (reservationId, paymentUrl, pricing). Integrates sibling tools and provides defaults. Missing only post-payment confirmation details, but given no output schema, it is quite complete.

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%, baseline 3. Description adds value by explaining quoteId's role ('lock the price'), paymentMode and channel defaults, and usage context for optional parameters like guestPhone.

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 explicitly states 'Create a booking with Stripe payment and return a checkout URL', providing a specific verb and resource. It clearly distinguishes from siblings like hemmabo_booking_create (no payment) and hemmabo_booking_status (status check).

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?

Clear usage guidance: 'Use this tool when the user is ready to pay', warns against double charges with 'Do NOT call twice for the same booking — check hemmabo_booking_status first', and suggests optional quoteId from hemmabo_booking_negotiate.

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/HemmaBo-se/hemmabo-mcp-server'

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