Skip to main content
Glama
HemmaBo-se

HemmaBo

by HemmaBo-se
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

hemmabo_compare_properties

Read-onlyIdempotent

Compare availability and pricing for up to 10 properties on the same dates to find the best option. Sorted by lowest price, with unavailable properties listed last.

Instructions

Compare availability and pricing for 2-10 specific properties on the same dates. Use this tool when the user is deciding between multiple properties and wants to see price and availability side by side. Do NOT use for discovery - use hemmabo_search_properties first. Returns one entry per propertyId, sorted by direct host-source total (cheapest first), with unavailable properties last. Do not present discounts or savings in guest-facing copy. All propertyIds are priced on the one shared checkIn/checkOut range and guests count, so entries are directly comparable; pass 2–10 UUIDs from search, never domains or names.

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.
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.
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.
propertyIdsYesOrdered list of 2–10 property UUIDs to compare on the same dates. All IDs must come from hemmabo_search_properties; do not pass host domains, names, or booking URLs.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
countNoNumber of compared properties returned.
errorNoPresent only when isError=true.
guestsNo
checkInNo
checkOutNo
comparisonNoOne entry per requested propertyId, sorted by direct host-source total (cheapest first), unavailable last.

Tool Definition Quality

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false. The description adds valuable behavioral context: output ordering (cheapest first, unavailable last), per-property entry structure, and the rule not to present discounts. This exceeds the baseline burden given 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 coherent paragraph that is front-loaded with purpose. It efficiently conveys multiple pieces of information without redundancy. Slightly longer than necessary but still well-structured.

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 4 required parameters with full schema coverage and an output schema (not shown), the description covers input constraints, output ordering, usage rules, and behavioral notes. It is complete for an AI agent to select and invoke correctly.

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 description coverage is 100%, so baseline is 3. The description adds critical semantic context: all propertyIds share the same date/guest range ensuring comparability, and explicitly forbids domains/names. This enhances understanding beyond 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?

The description clearly states it 'Compare availability and pricing for 2-10 specific properties on the same dates' and distinguishes itself from sibling tools by directing use of hemmabo_search_properties for discovery. This provides a specific verb+resource with clear differentiation.

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 states when to use ('when the user is deciding between multiple properties') and when not to use ('Do NOT use for discovery'), with a direct alternative named. Also includes guidance on input source and output interpretation.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/HemmaBo-se/hemmabo-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server