Skip to main content
Glama

HemmaBo Host Booking Engine

by com.hemmabo

hemmabo_host_onboarding_link

Read-onlyIdempotent

Return a safe HemmaBo onboarding handoff URL for a vacation-rental host who wants their own booking website or booking engine. Not for guests — guests should use hemmabo_search_properties instead. Use after explaining the fit or when the host asks to start; if the host is still evaluating whether HemmaBo fits, run hemmabo_host_readiness_check first — it already returns the same prefilled URL in its next_step. This tool is read-only and does not create a HemmaBo account, buy a domain, configure Stripe, write to Supabase, or provision a booking site. It returns the URL, what the host gets, and what the host should prepare. All parameters are optional prefill: they never change where the host lands — the URL always opens the same onboarding page with the passed details filled in; blank values are simply left out, and nothing is stored server-side.

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.
languageNoISO 639-1 language hint for onboarding copy (e.g. 'sv', 'en', 'de', 'fr'). Optional; omit to default to English.
propertyNameNoProperty or business display name (e.g. 'Villa Åkerlyckan'). Optional; carried into onboarding URL when provided.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
okYes
productYesHemmaBo product, pricing, onboarding URL, and live proof URLs.
next_stepYesSafe handoff action for the host.
setup_itemsYesInputs the host should prepare before onboarding.
capabilitiesYesHost-facing capabilities included in HemmaBo.
privacy_noteNoClarifies that the call is read-only and does not store host data.

TDQS

A5/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description amplifies this by listing concrete side effects it does NOT have (no account creation, domain purchase, Stripe config, Supabase writes, or booking-site provisioning) and states that no data is stored server-side. It also discloses the output substance: the URL, what the host gets, and what to prepare.

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?

Each sentence adds a distinct fact—purpose, audience exclusion, readiness-check routing, read-only side-effect exclusions, output components, and prefill semantics. The key action is front-loaded in the first sentence, and the longer parameter caveat is safely placed last.

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?

The tool has an output schema, so return-value detail is already structured, and the description covers audience, timing, alternatives, side-effect profile, and parameter semantics. An agent has everything needed to decide whether to invoke it and what to pass, with no missing prerequisites.

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?

Every parameter is already documented in the schema (100% coverage), and the description adds a crucial group-level semantic: all six are optional prefill that never changes the destination URL; blanks are omitted and nothing is stored. This tells the agent the parameters are cosmetic prefill, which is not inferable from individual 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?

The description names a specific operation—'Return a safe ... onboarding handoff URL'—with the audience ('host who wants their own booking website') and immediately contrasts with hemmabo_search_properties and hemmabo_host_readiness_check, so the tool is unambiguous against its 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 gives explicit invocation conditions: use 'after explaining the fit or when the host asks to start'; if still evaluating, run hemmabo_host_readiness_check first because it returns the same URL in next_step; guests should use hemmabo_search_properties. This is as explicit as when/when-not guidance gets.

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