Skip to main content
Glama

HemmaBo Host Booking Engine

by com.hemmabo

hemmabo_host_readiness_check

Read-onlyIdempotent

Read-only fit check for a vacation-rental host evaluating HemmaBo for their own booking website or booking engine. Use when the user is a host or property owner, not a guest booking a stay; guests should use hemmabo_search_properties instead. Returns a fit verdict, what the host gets, the setup inputs to prepare, and a safe onboarding next step. Does not create an account, buy a domain, configure Stripe, store host data, or provision a website. When the host is ready to start, follow up with hemmabo_host_onboarding_link. Only five inputs sharpen the fit verdict: a domain (hasOwnDomain or domain), currentChannels, one location signal (city/region/country), and the wants* booleans, which count unless explicitly false — omitting them never lowers the verdict; propertyName and preferredLanguage only prefill the onboarding URL, and with no inputs the summary is generic.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cityNoCity or municipality (e.g. 'Kävlinge', 'Florence'). Optional; used in onboarding URL prefill when provided.
domainNoHost-owned domain without protocol or path (e.g. 'villaakerlyckan.se', 'myvilla.it'). Optional; omit when the host has not chosen a domain yet. Invalid: 'https://...', paths, ports, or booking URLs.
regionNoRegion or area (e.g. 'Skåne', 'Toscana', 'Marrakech-Safi'). Optional; narrows onboarding handoff and proof examples.
countryNoCountry where the property operates (e.g. 'Sweden', 'Italy', 'Morocco'). Optional; improves onboarding URL locale and fit assessment.
hasOwnDomainNoTrue if the host already owns a domain or explicitly wants one (e.g. true for 'I have villaakerlyckan.se'). False or omit when still undecided.
propertyNameNoProperty or business display name (e.g. 'Villa Åkerlyckan'). Optional; carried into onboarding URL when provided.
propertyTypeNoProperty category enum. Optional; omit when unknown. 'villa'/'holiday_home' fit best; 'hotel' may indicate a poor HemmaBo fit for large chains.
currentChannelsNoOptional list of channels the host uses today. Omit when unknown. Helps assess migration fit from OTAs to their own booking website.
preferredLanguageNoISO 639-1 language hint for onboarding copy (e.g. 'sv', 'en', 'de', 'fr'). Optional; omit to default to English.
wantsAiAgentBookingNoTrue if the host wants AI agents (ChatGPT, Claude, Cursor) to discover and book via their own official website. False or omit when they only want a guest website.
wantsDirectPaymentsNoTrue if the host wants Stripe Connect payouts direct to their account. False or omit when they expect HemmaBo to be merchant of record (not supported).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
okYesTrue when the fit check completed.
productYesHemmaBo product summary, pricing, onboarding URL, and live proof URLs.
next_stepYesSafe handoff action for the host.
readinessYesFit verdict and boundaries for the host's described need.
setup_itemsYesInputs the host should prepare before onboarding.
capabilitiesYesHost-facing capabilities included in HemmaBo.
agent_instructionYesHow an AI agent should describe HemmaBo without overclaiming.

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, and the description consistently reinforces the read-only nature ('Does not create an account, buy a domain, configure Stripe, store host data, or provision a website'). It adds behavioral detail beyond the annotations: the safe onboarding next step, the omission semantics of wants* booleans ('count unless explicitly false — omitting them never lowers the verdict'), and what happens with no inputs ('summary is generic'). No contradiction with annotations.

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 a single dense paragraph that front-loads the verb, scope, and user audience, then proceeds to exclusions, return contents, and parameter semantics. It is longer than the typical ideal, but every clause earns its place—there is little redundancy and it packs meaningful routing and behavior detail. A bulleted or two-paragraph structure would improve scannability, but the density is justified.

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 the tool has 11 optional parameters, no required inputs, an output schema, and strong annotations, the description covers all decision-relevant aspects: who should use it, what it returns, what it does NOT do, what input changes the result, what happens with no input, and which sibling to invoke next. The output schema covers return values, so no return-format detail is needed. Nothing an agent needs to call it 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 the baseline is 3, but the description adds valuable cross-parameter semantics above the schema: it groups all 11 params into 'five inputs that sharpen the fit verdict' vs 'only prefill the onboarding URL', explains that wants* booleans count unless explicitly false, and clarifies that omitting them never lowers the verdict. That is genuinely additive meaning, not schema repetition, though it doesn't enumerate every parameter by name.

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 begins with a crisp verb+object ('Read-only fit check') and names the exact target user (vacation-rental host) and product context (HemmaBo for their own booking website/booking engine). It explicitly contrasts with the guest-facing sibling hemmabo_search_properties, so an agent can disambiguate the tool without reading schemas. It also names the follow-up sibling (hemmabo_host_onboarding_link).

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 states when to use ('when the user is a host or property owner'), when not to use ('not a guest booking a stay; guests should use hemmabo_search_properties instead'), and what the next tool is when the host is ready ('follow up with hemmabo_host_onboarding_link'). It also clarifies which inputs sharpen the verdict versus which only prefill the onboarding URL, giving an agent actionable routing guidance.

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