HemmaBo Host Booking Engine

Search Properties

hemmabo_search_properties

Read-onlyIdempotent

Search available vacation rental properties by location and travel dates. Use when the user wants to find or browse places to stay. Discovery only — call get_verified_stay_offer with the host domain and same dates before the final answer so the client can render the verified stay offer widget; never quote a final price or booking link from search alone. Do NOT use when the user already has a propertyId or host domain. Returns propertyId, host domain, live availability, host-source pricing, and capacity. Parameters combine as one filter with guests and the checkIn/checkOut range (checkIn strictly before checkOut): region matches broadly against region, city, and country names, while country matches the country field alone — omit both and the search spans every published property. Capacity misses are excluded; date-unavailable matches return separately in unavailableMatches with up to three alternative windows.

Input Schema

TableJSON Schema

Name	Required	Description
`guests`	Yes	Total guest count as a positive integer (e.g. 2, 4, 6). Used for capacity filtering and staircase pricing tiers. Properties with maxGuests below this value are excluded from search results.
`region`	No	Region, area, or destination to search within (e.g. 'Skåne', 'Kävlinge', 'Toscana', 'Bavaria'). Partial case-insensitive match. Provide at least one of region or country; omit only when country alone is sufficient.
`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.
`country`	No	Country name to filter by (e.g. 'Sweden', 'Italy', 'Morocco'). Partial case-insensitive match. Provide at least one of region or country; omit when region already narrows the destination.
`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.

Output Schema

TableJSON Schema

Name	Required	Description
`error`	No	Present only when isError=true.
`guests`	No	Echoed guest count.
`checkIn`	No	Echoed check-in date (YYYY-MM-DD).
`checkOut`	No	Echoed check-out date (YYYY-MM-DD).
`properties`	No	Available properties matching the search criteria, with live host-source pricing.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 1, 2026

addedOutput schema / properties / properties / items / properties / booking_url

Added value: +{
+  "description": "The host's own booking URL: https:// plus the host-owned domain. Null when the property has no domain.",
+  "format": "uri",
+  "type": [
+    "string",
+    "null"
+  ]
+}

changedOutput schema / properties / properties / items / properties / propertyId / description

Previous value: -"Stable UUID. Pass to subsequent tools (availability, quote, checkout)."New value: +"Stable UUID. Pass to subsequent tools (availability)."

First observedSep 1, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Adds rich context beyond annotations: read-only is covered by annotations, but the description adds that search alone must never quote a final price or booking link, that date-unavailable matches return separately in unavailableMatches with up to three alternative windows, and that capacity misses are excluded. This is exactly the behavioral detail annotations do not cover.

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?

Well front-loaded: purpose first, then usage, then behavioral warnings, then parameter mechanics. Dense but every clause carries information. Slightly long but justified by the multi-part semantics.

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?

Covers purpose, usage, routing to sibling, return fields (propertyId, host domain, availability, pricing, capacity), edge cases (capacity misses excluded, date-unavailable matches in unavailableMatches), and parameter interaction. An output schema exists but the description still appropriately summarizes returns. Nothing an agent needs to call this correctly is missing.

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%, so baseline is 3. The description still adds value by specifying how region and country combine (region matches broadly against region/city/country; country matches country alone; omitting both spans all properties), and that checkIn is strictly before checkOut. This is useful cross-parameter logic not fully captured in 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?

States a specific verb (search) and resource (vacation rental properties) with scope (by location and travel dates). Explicitly distinguishes from siblings by naming get_verified_stay_offer as the required follow-up and stating this is discovery only.

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?

Front-loads when to use ('find or browse places to stay') and when not ('already has a propertyId or host domain'). Also names the mandatory alternative workflow (call get_verified_stay_offer before final answer), leaving nothing ambiguous.

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

All HemmaBo Host Booking Engine tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.