Skip to main content
Glama

hemmabo_booking_status

Read-onlyIdempotent

Retrieve current status and full details of an existing booking by providing its reservationId and guestToken. Use this to confirm checkout/create success or before canceling/rescheduling, but do not use for property discovery or pricing.

Instructions

Retrieve current status and full details of an existing booking by reservationId. Use to confirm checkout/create succeeded or before cancel/reschedule. Do NOT use for property discovery, availability, or pricing — use hemmabo_search_properties, hemmabo_search_availability, or hemmabo_booking_quote for those. Requires Authorization: Bearer token (MCP_API_KEY or OAuth); rate-limited per token. Read-only against the database — never writes, so it is safe to poll after a checkout timeout — but returns guest PII (name, email). reservationId is the booking UUID returned by hemmabo_booking_checkout or hemmabo_booking_create — never a propertyId — and guestToken is the secret issued with that same booking: a mismatched pair reveals nothing, not even that the booking exists. Without a reservationId there is no booking to look up yet.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
guestTokenYesPer-booking secret returned by hemmabo_booking_create / hemmabo_booking_checkout (the booking's guest_token, a UUID). Required to view or modify this specific booking — a valid Bearer token alone is NOT sufficient, because it authenticates the caller but grants no authority over any particular booking. Present the exact guestToken you received when the booking was created; without the matching value the call is refused. Never a propertyId or reservationId.
reservationIdYesBooking or reservation UUID from hemmabo_booking_checkout or hemmabo_booking_create (e.g. '7c9e6679-7425-40de-944b-e07fc1f90ae7'). Required to look up, cancel, or reschedule the same booking record.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
errorNoPresent only when isError=true.
guestsNoBooked guest count.
statusYesHost-node booking status. 'completed' is a protocol compatibility output only, not the active lifecycle truth.
checkInNoBooked arrival date.
checkOutNoBooked departure date.
currencyNoISO 4217 currency code for the booking total.
createdAtNoBooking creation timestamp.
guestNameNoPrimary guest name stored on the booking.
updatedAtNoLast update timestamp for the booking record.
guestEmailNoPrimary guest email stored on the booking.
propertyIdNoProperty UUID associated with the booking.
totalPriceNoTotal amount in minor currency units.
propertyNameNoDisplay name of the booked property.
reservationIdYesEchoed booking or reservation UUID.
propertyDomainNoHost-owned domain associated with the property.
cancellationPolicyNoHost cancellation-policy details applicable to this booking.
Behavior5/5

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

Beyond the annotations (readOnly, idempotent, non-destructive), the description discloses that it returns guest PII, is safe to poll, requires a Bearer token, and explains the guestToken requirement in depth. This significantly exceeds annotation-only transparency.

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 packed with pertinent information, each sentence contributing unique value. It is front-loaded with the primary purpose and use cases, maintaining clarity without 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?

The description provides complete context for invocation: when to use, safety, auth, parameter origins, and behavioral implications. Since an output schema exists, not explaining the return value is acceptable.

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?

Both parameters have detailed schema descriptions covering format, source, and necessity. The description adds further clarification that reservationId is never a propertyId and guestToken is a per-booking secret, enriching 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 clearly states the tool retrieves current status and full details of an existing booking by reservationId, and explicitly distinguishes it from discovery, availability, and pricing tools. It names the specific sibling tools to avoid confusion.

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 gives explicit when-to-use guidance (confirm checkout/create, before cancel/reschedule) and when-not-to-use guidance, pointing to alternative tools. It also notes the required authorization and rate limiting.

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