HemmaBo

hemmabo_booking_negotiate

Lock a fixed host price for 15 minutes to prevent changes during checkout. Requires property ID, check-in/out dates, and guest count. Returns alternative bookable dates if the requested stay is unavailable.

Instructions

PRICE LOCK, not negotiation: the host's price is fixed — this tool never bargains, discounts, or alters it; it only freezes the current host-source price for 15 minutes so it cannot change during checkout. It refuses to lock dates the property's calendar cannot deliver and returns alternative bookable windows instead. Use it only in the non-VRP fallback checkout flow, 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); rate-limited per token. Not idempotent: each call writes a new snapshot; validUntil is fixed at creation and never extended — re-locking returns a new quoteId. The lock freezes both the public and the direct host-source total; hemmabo_booking_checkout's channel picks which one is redeemed. Redeem the quoteId only for the identical propertyId + checkIn/checkOut + guests, and only until validUntil — changing any of them requires a new quote. Night count and guest count together select the locked price tier.

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

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedv0.1.6Jun 28, 2026

removedInput schema / $schema

Removed value: -"http://json-schema.org/draft-07/schema#"

addedInput schema / additionalProperties
```
Added value: +false
```
removedInput schema / properties / guests / maximum
```
Removed value: -9007199254740991
```

removedInput schema / properties / propertyId / pattern

Removed value: -"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "breakdown": {
+      "additionalProperties": true,
+      "type": "object"
+    },
+    "checkIn": {
+      "type": "string"
+    },
+    "checkOut": {
+      "type": "string"
+    },
+    "currency": {
+      "type": "string"
+    },
+    "error": {
+      "description": "Present only when isError=true.",
+      "type": "string"
+    },
+    "federationDiscountPercent": {
+      "type": "integer"
+    },
+    "federationTotal": {
+      "type": "integer"
+    },
+    "gapDiscountPercent": {
+      "type": "integer"
+    },
+    "gapNight": {
+      "type": "boolean"
+    },
+    "gapTotal": {
+      "type": "integer"
+    },
+    "guests": {
+      "type": "integer"
+    },
+    "nights": {
+      "type": "integer"
+    },
+    "packageApplied": {
+      "type": "string"
+    },
+    "propertyId": {
+      "format": "uuid",
+      "type": "string"
+    },
+    "publicTotal": {
+      "type": "integer"
+    },
+    "quoteId": {
+      "description": "Snapshot ID. Pass to hemmabo_booking_checkout to lock this price.",
+      "type": "string"
+    },
+    "validUntil": {
+      "description": "Quote expiry (ISO 8601). Typically 15 minutes after creation.",
+      "format": "date-time",
+      "type": "string"
+    }
+  },
+  "required": [
+    "quoteId",
+    "validUntil",
+    "federationTotal"
+  ],
+  "type": "object"
+}

Changed3 schema fields changedv0.1.5Jun 15, 2026

changedInput schema / properties / checkIn / description

Previous value: -"Arrival date in ISO 8601 format (YYYY-MM-DD, e.g. '2026-07-15'). Must be today or later."New value: +"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."

changedInput schema / properties / checkOut / description

Previous value: -"Departure date in ISO 8601 format (YYYY-MM-DD, e.g. '2026-07-22'). Must be after checkIn."New value: +"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."

changedInput schema / properties / propertyId / description

Previous value: -"Stable property UUID returned by hemmabo_search_properties. Use the exact UUID, not the property name, domain, or booking URL."New value: +"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."

Changed1 schema field changedv0.1.4Jun 9, 2026

changedInput schema / properties / propertyId / description

Previous value: -"Property UUID from hemmabo_search_properties (e.g. '550e8400-e29b-41d4-a716-446655440000')."New value: +"Stable property UUID returned by hemmabo_search_properties. Use the exact UUID, not the property name, domain, or booking URL."

Changed1 schema field changedv0.1.3May 19, 2026

changedInput schema / properties / propertyId / description

Previous value: -"Property UUID from search.properties (e.g. '550e8400-e29b-41d4-a716-446655440000')."New value: +"Property UUID from hemmabo_search_properties (e.g. '550e8400-e29b-41d4-a716-446655440000')."

Addedv0.1.1May 19, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Despite sparse annotations, the description discloses auth requirements, rate limiting, non-idempotence, snapshot creation, fixed validUntil, refusal on unavailable calendar dates, and the dual public/direct total freeze. It also clarifies redemption constraints and downstream checkout behavior, going far beyond what annotations provide.

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?

Although long, every sentence adds a distinct operational fact and there is no filler. The critical scoping correction is front-loaded, followed by usage conditions, side effects, and redemption constraints in logical order.

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 non-idempotent, auth-required, time-boxed quote tool, the description covers when to call it, when never to call it, prerequisites, side effects, expiry behavior, exact-match requirements, and downstream checkout interaction. Since an output schema exists, not explaining return values is acceptable.

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 descriptions already cover all four parameters, so the baseline is 3. The description adds value by explaining that the quote is bound to the exact propertyId/checkIn/checkOut/guests combination and that night count plus guest count jointly select the price tier.

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 opening line 'PRICE LOCK, not negotiation' explicitly corrects the misleading tool name and defines the operation as freezing the host-source price for 15 minutes. It identifies the exact resource and distinguishes this tool from checkout and verified-offer siblings.

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?

It explicitly says 'Use it only in the non-VRP fallback checkout flow, when no signed direct_booking_url is available and the user explicitly asks to lock a price' and gives a precise never-use list. It also names get_verified_stay_offer as the alternative for verified-offer display, leaving no judgment call.

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

Deploy Server

hemmabo_booking_negotiate

Instructions

Input Schema

Output Schema

Schema Changelog

TDQS

Other Tools