Skip to main content
Glama

OpenStays Property Passports

Search OpenStays accommodation

search_stays
Read-onlyIdempotent

Search public Property Passports within one country or territory. Country alone is enough. Town, region, bedrooms, guest capacity and property type are optional refinements. Returns up to 10 matching accommodation units, preferring different Property Passports. No catalogue export, total count or pagination. Search does not filter by dates or check live prices. A Passport lists booked dates when the owner shares a calendar.

Input Schema

NameRequiredDescriptionDefault
countryNoOne country or territory name or supported exact alias, for example New Zealand or NZ.
minGuestsNo
destinationNoA country, locality or region. Without country, this must identify one country among public Passport locations. With country, use this for an optional locality or region.
minBedroomsNo
propertyTypeNoPublic accommodation type, for example villa or cottage.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Beyond the annotations (readOnly, openWorld, idempotent, non-destructive), the description discloses the result cap of 10, the preference for distinct Property Passports, the absence of pagination and total counts, and that prices and availability are not checked. The note that a Passport lists booked dates only when the owner shares a calendar is genuinely non-obvious behavioral context.

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?

Front-loaded with the core operation and then terse, high-density constraint sentences; essentially no filler. The telegraphic fragments ('No catalogue export, total count or pagination') read slightly clipped, but each sentence carries distinct information.

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?

For a read-only search with no output schema, the definition covers scope, result limits, ranking behavior and known non-capabilities well enough to call correctly. The remaining gap is the missing explicit routing versus get_property_passport, plus no guidance on what happens when a search yields no country match.

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?

With 60% schema description coverage, the schema already documents country, destination and propertyType. The description adds useful framing that town/region, bedrooms, guest capacity and property type are optional refinements, but it does not clarify the anyOf rule that destination alone can satisfy the call, which is the least intuitive part of the schema.

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?

States a specific verb and resource: searching public Property Passports scoped to one country or territory, and clarifies that matching is at accommodation-unit level. The purpose is unambiguous, but it never names or contrasts with the sibling get_property_passport, leaving the agent to infer the division of labor.

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?

Gives a clear entry condition (country alone is enough) and enumerates optional refinements, plus explicit exclusions: no date filtering, no live prices, no pagination or total count. It stops short of explicit when-to-use-this-instead guidance relative to get_property_passport.

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