Skip to main content
Glama

Stay details

stay_details
Read-onlyIdempotent

Read a Guestit apartment or holiday home in Sweden, including all public amenities, house rules, cancellation policy and a dated price estimate. Use this to check a home’s amenities and conditions before recommending it. Supply both dates and the guest count for an estimate. Fees shown are already included in the total. This does not reserve inventory or take payment. Open website_url to continue on Guestit; it opens with the dates and guests filled in.

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_slug": "<listing_slug>",
      "num_guests": "<num_guests>"
    },
    "name": "stay_details"
  }
}

Input Schema

NameRequiredDescriptionDefault
localeNoen
end_dateNoYYYY-MM-DD. Supply both dates. Check-in must be within 730 days and the stay cannot exceed 730 nights.
num_guestsYes
start_dateNoYYYY-MM-DD. Supply both dates. Check-in must be within 730 days and the stay cannot exceed 730 nights.
listing_slugYes

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.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, and the description adds genuinely new behavioral facts: fees are already in the total, no inventory is reserved, no payment is taken, and website_url opens prefilled with dates and guests. It stops short of return shape or pagination details, but that is largely covered by the output schema.

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 one-idea sentences, front-loaded with the resource and its returned content, then usage, then the payment/reservation disclaimer, then the hand-off instruction. Nothing is redundant, though the final website_url sentence could be phrased more tightly.

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?

With an output schema present, the description rightly focuses on scope, preconditions, and the no-reservation/no-payment boundary. The remaining gaps are the locale parameter's effect on returned content and the listing_slug identifier format, which an agent would still have to guess.

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 40%, so the description must add meaning and it partially does: it ties start/end dates and num_guests to the price estimate and states both dates are needed. It says nothing about locale (the only enum) or the format and role of listing_slug, leaving two parameters undocumented in both places.

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 gives a specific verb and resource ('Read a Guestit apartment or holiday home in Sweden') and enumerates what is returned (amenities, house rules, cancellation policy, dated price estimate). It implies the pre-booking inspection role relative to search, but never names its siblings, so the differentiation is inferred rather than stated.

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

Usage Guidelines4/5

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

'Use this to check a home's amenities and conditions before recommending it' establishes clear context of use, and 'Supply both dates and the guest count for an estimate' states a precondition. There is no explicit when-not-to-use or named alternative (e.g. compare_stays), so full routing guidance is absent.

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