HemmaBo

Host Readiness Check

hemmabo_check_host_readiness

Read-only

Check whether HemmaBo fits a vacation-rental host before onboarding. Returns a fit verdict, setup inputs, and a safe next step for launching their own booking website.

Instructions

Use this tool when a host is still EVALUATING whether HemmaBo fits; use hemmabo_get_host_onboarding_link only when the host has decided and wants to start. Never call both in the same turn — this tool's next_step already contains the same onboarding URL. 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_get_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. Booking and payment happen only on the host's own domain, at the signed direct_booking_url. The agent never books, pays, cancels or changes a booking.

Input Schema

TableJSON Schema

Name	Required	Description
`city`	No	City or municipality (e.g. 'Kävlinge', 'Florence'). Optional; used in onboarding URL prefill when provided.
`domain`	No	Host-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.
`region`	No	Region or area (e.g. 'Skåne', 'Toscana', 'Marrakech-Safi'). Optional; narrows onboarding handoff and proof examples.
`country`	No	Country where the property operates (e.g. 'Sweden', 'Italy', 'Morocco'). Optional; improves onboarding URL locale and fit assessment.
`hasOwnDomain`	No	True 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.
`propertyName`	No	Property or business display name (e.g. 'Villa Åkerlyckan'). Optional; carried into onboarding URL when provided.
`propertyType`	No	Property category enum. Optional; omit when unknown. 'villa'/'holiday_home' fit best; 'hotel' may indicate a poor HemmaBo fit for large chains.
`currentChannels`	No	Optional list of channels the host uses today. Omit when unknown. Helps assess migration fit from OTAs to their own booking website.
`preferredLanguage`	No	ISO 639-1 language hint for onboarding copy (e.g. 'sv', 'en', 'de', 'fr'). Optional; omit to default to English.
`wantsAiAgentBooking`	No	True 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.
`wantsDirectPayments`	No	True 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

Name	Required	Description
`ok`	Yes	True when the fit check completed.
`product`	Yes	HemmaBo: the category sentence, the host's subscription price atom, and the onboarding URL.
`next_step`	Yes	Safe handoff action for the host.
`readiness`	Yes	Fit verdict and boundaries for the host's described need.
`agent_role`	Yes	What a compatible agent does: discover the host domain, verify the signed stay offer, send the guest to that domain to book. The agent does not book.
`setup_items`	Yes	Inputs the host should prepare before onboarding.
`agent_instruction`	Yes	How an AI agent should describe HemmaBo without overclaiming.

Schema Changelog

Changes observed during successful MCP inspections.

Addedv7.0.5Oct 14, 2026

TDQS

A5/5.0

Behavior5/5

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

Annotations confirm read-only safety, and the description adds substantial non-obvious behavior: it does not create accounts, buy domains, configure Stripe, store host data, or provision websites; booking and payment occur only on the host's own signed direct_booking_url; and the agent never books, pays, cancels, or changes bookings. It also discloses that this tool's next_step already includes the onboarding URL, preventing a duplicate tool call.

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?

Front-loads the triggering condition and the sibling routing rule, then layers scope, exclusions, and parameter weighting. Although long, every sentence carries routing, behavioral, or parameter semantics, and there is no filler or restatement of the structured schema.

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 an 11-parameter tool with an output schema, rich annotations, and five sibling tools, the description covers selection, exclusion, behavioral boundaries, parameter effects, and next-step coordination. Nothing an agent needs in order to call it correctly or avoid a duplicate call is missing.

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?

Though the schema already documents every parameter, the description adds semantic grouping and omission behavior the schema does not: only domain/hasOwnDomain, currentChannels, one location signal, and wants* booleans sharpen the verdict; wants* count unless explicitly false; omissions never lower the verdict; propertyName and preferredLanguage only prefill the onboarding URL; and no inputs produce a generic summary.

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 ('read-only fit check for a vacation-rental host evaluating HemmaBo') and distinguishes itself from siblings by naming hemmabo_get_host_onboarding_link and hemmabo_search_properties with the conditions that select each. An agent can route correctly without opening any schema.

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 says when to use this tool ('when a host is still EVALUATING'), when not to use it ('only when the host has decided'), names the alternative for each case, and adds a hard coordination rule: never call both in the same turn. Also excludes guests by routing them to hemmabo_search_properties.

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

Deploy Server