Skip to main content
Glama

HemmaBo Host Booking Engine

by com.hemmabo

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
NameRequiredDescriptionDefault
guestsYesTotal 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.
regionNoRegion, 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.
checkInYesArrival 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.
countryNoCountry 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.
checkOutYesDeparture 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
NameRequiredDescriptionDefault
errorNoPresent only when isError=true.
guestsNoEchoed guest count.
checkInNoEchoed check-in date (YYYY-MM-DD).
checkOutNoEchoed check-out date (YYYY-MM-DD).
propertiesNoAvailable properties matching the search criteria, with live host-source pricing.

TDQS

A4.9/5.0
Behavior5/5

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

Annotations declare readOnlyHint=true and idempotentHint=true, but the description adds significant behavioral nuance: 'Discovery only', 'never quote a final price', 'Capacity misses are excluded', and 'date-unavailable matches return separately in unavailableMatches with up to three alternative windows'. These details are not present in annotations and help set agent expectations.

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?

The description is dense but efficient—every sentence carries purpose, front-loaded with purpose and usage. Slightly verbose with overlapping statements ('Discovery only' and 'never quote a final price'), but it remains focused and scannable.

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, exclusions, workflow, return content, and parameter interaction. With an output schema and read-only annotations already present, the description provides everything an agent needs to select and invoke this tool correctly.

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?

Schema coverage is 100%, but the description enriches semantics: it explains how params combine into a single filter, clarifies region vs country matching behavior ('region matches broadly... while country matches the country field alone'), and documents the effect of omitting both ('search spans every published property'). This goes well beyond the schema descriptions.

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 and resource: 'Search available vacation rental properties by location and travel dates.' It also differentiates from siblings by defining the exact use case ('find or browse places to stay') and explicitly routing away when a propertyId or host domain already exists.

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?

Provides explicit when-to-use ('Use when the user wants to find or browse places to stay'), when-not-to-use ('Do NOT use when the user already has a propertyId or host domain'), and a workflow directive (call get_verified_stay_offer before final answer, never quote price from search alone). This gives an agent unambiguous decision criteria.

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 toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.8/5.0
Disambiguation4/5

Most tools are cleanly separated by lifecycle stage (search, availability, quote, lock, checkout, status, cancel, reschedule), but get_verified_stay_offer, hemmabo_booking_quote, and hemmabo_booking_negotiate all touch pricing and could be confused in a quick selection. The descriptions do a strong job of disambiguating them, so only one or two pairs are genuinely ambiguous.

Naming Consistency4/5

The vast majority follow a consistent hemmabo_<domain>_<action> pattern with snake_case throughout. Minor deviations exist: hemmabo_booking_status is a noun rather than a verb, and get_verified_stay_offer / verify_vacation_rental_node break the hemmabo_ prefix convention.

Tool Count5/5

13 tools is well within the ideal range for a booking engine. Each tool maps to a distinct step in the guest journey or host onboarding flow, and none feel redundant or purely decorative.

Completeness5/5

The tool surface covers the full guest lifecycle: discovery, availability, pricing, price locking, checkout, pending booking creation, status lookup, cancellation, and rescheduling. Host-side onboarding is also represented, and the VRP verification/offer tools complete the trust and signed-offer path without leaving obvious dead ends.

Resources