Skip to main content
Glama

Compare stays

compare_stays
Read-onlyIdempotent

Compare two to four distinct Guestit apartments or holiday homes in Sweden for the same dates and guest count. Includes all public amenities, house rules and cancellation policies. Retains missing or unavailable listings. Prices include applicable fees and do not hold inventory or confirm a booking.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "listing_slugs": "<listing_slugs>",
      "num_guests": "<num_guests>",
      "start_date": "<start_date>",
      "end_date": "<end_date>"
    },
    "name": "compare_stays"
  }
}

Input Schema

NameRequiredDescriptionDefault
localeNoen
end_dateYesYYYY-MM-DD. Supply both dates. Check-in must be within 730 days and the stay cannot exceed 730 nights.
num_guestsYes
start_dateYesYYYY-MM-DD. Supply both dates. Check-in must be within 730 days and the stay cannot exceed 730 nights.
listing_slugsYes

Output Schema

NameRequiredDescriptionDefault
viewYes
staysYes
localeYesen
paginationYes
destinationsYes
calculated_atYes
requested_stayYes
applied_filtersYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description still adds real behavioral context beyond them: unavailable listings are retained rather than dropped, prices include applicable fees, and the call neither holds inventory nor confirms a booking. Only the handling of invalid or unknown slugs is left unstated.

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?

Four short sentences, front-loaded with the core action and cardinality, then behavior, then the price/booking caveat. Every sentence adds something; no filler or repetition of the tool name.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need not be explained, and the description covers the important behavioral traits for a read-only comparison call. The gaps are modest: slug sourcing and locale semantics, both of which an agent would need to construct a valid first call.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 40%, so the description carries extra burden. It does reinforce that listings must be distinct and share a date range and guest count, matching the schema constraints, but it never explains the slug format, where to obtain slugs, or what the locale parameter controls.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb ('Compare'), the resource (Guestit apartments or holiday homes), the cardinality (two to four distinct listings), and the shared constraints (same dates and guest count). That is far more precise than the title alone. It does not explicitly contrast itself with search_stays or stay_details, so it stops short of a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The preconditions for calling it (2-4 distinct listings, one shared date range, one guest count) are stated, which implies when it applies. But there is no explicit when-to-use versus search_stays or stay_details, and no statement about where the slugs should come from or what to do if fewer than two listings match.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources