HemmaBo

hemmabo_booking_negotiate

Create a binding price quote that locks the price for 15 minutes for fallback checkout deployments. Use only when no signed direct booking URL is available and price locking is required.

Instructions

Create a binding price quote that locks the price for 15 minutes for configured non-VRP fallback checkout deployments. Use only when no signed direct_booking_url is available and the user explicitly asks to lock a price. Never use this for search, availability, VRP offers, rendering a stay-offer widget, or verified-offer display — use get_verified_stay_offer instead. Requires Authorization: Bearer token (MCP_API_KEY or OAuth). Writes a short-lived quote snapshot server-side. Rate-limited per token. Locks the propertyId's price for the exact checkIn/checkOut range and guests; the returned quoteId encodes that combination and is honored by hemmabo_booking_checkout only until validUntil.

Input Schema

TableJSON Schema

Name	Required	Description
`guests`	Yes	Total number of guests as integer >= 1 (e.g. 4). Determines which price tier is applied.
`checkIn`	Yes	Arrival date in ISO 8601 calendar format YYYY-MM-DD (e.g. '2026-07-15'). Must be today or later in the property's timezone. Must be strictly before checkOut; together they define the stay length used for pricing and availability.
`checkOut`	Yes	Departure date in ISO 8601 calendar format YYYY-MM-DD (e.g. '2026-07-22'). Must be strictly after checkIn on the same calendar. The guest does not stay the departure night.
`propertyId`	Yes	Stable property UUID from hemmabo_search_properties (e.g. '550e8400-e29b-41d4-a716-446655440000'). Pass the exact UUID string — never a property name, host domain, or booking URL.

Output Schema

TableJSON Schema

Name	Required	Description
`error`	No	Present only when isError=true.
`guests`	No
`nights`	No
`checkIn`	No
`quoteId`	Yes	Snapshot ID. Pass to hemmabo_booking_checkout to lock this price.
`checkOut`	No
`currency`	No
`gapNight`	No
`gapTotal`	No
`breakdown`	No
`propertyId`	No
`validUntil`	Yes	Quote expiry (ISO 8601). Typically 15 minutes after creation.
`publicTotal`	No
`packageApplied`	No
`federationTotal`	Yes
`gapDiscountPercent`	No
`federationDiscountPercent`	No

Tool Definition Quality

A4.6/5.0

Behavior5/5

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

Description adds behavioral context beyond annotations: locks price for 15 minutes, writes a short-lived quote server-side, rate-limited, quoteId honored by checkout until validUntil. No contradiction with annotations (readOnlyHint=false, destructiveHint=false).

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?

Description is concise yet informative; each sentence adds value. Slightly long but well-structured and front-loaded with core purpose.

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 tool complexity and sibling context, description is highly complete: covers usage conditions, behaviors, auth, rate limits, and relationship to checkout. Output schema likely covers return structure.

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 covers 100% of parameters with detailed descriptions. Description does not add significant new meaning beyond what schema already provides, so baseline 3 is appropriate.

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?

Description clearly states it creates a binding price quote that locks the price for 15 minutes, explicitly distinguishes from sibling get_verified_stay_offer by specifying what the tool is and isn't for.

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?

Explicitly states when to use (only when no direct_booking_url and user asks to lock price) and when not to use (search, availability, VRP, etc.), with clear alternative named. Also notes auth requirements and rate limits.

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

Your AI Chatbot Just Exposed Your CEO's Salary to an Intern
By Om-Shree-0709 on July 2, 2026.
Agent Identity
MCP Security
OAuth Delegation
Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)
By Om-Shree-0709 on June 30, 2026.
Agentic Ai
Prompt Injection
WebAssembly
Lightport: Open-Sourcing Glama's AI Gateway
By punkpeye on April 27, 2026.
OpenAI
open source

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