Skip to main content
Glama

Find furnished stays

search_hyatus_stays
Read-only

Search public Hyatus stays by location, dates, guests, or amenities. Results include nextOffset for another page with the same filters.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_hyatus_stays"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
offsetNo
filtersNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is covered by structured data. The description adds genuinely new behavior: results carry a nextOffset for paging with the same filters. It still says nothing about rate limits, auth needs, or result size/shape, which caps it at a 3.

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?

Two sentences, zero filler, with the scope and filterable dimensions front-loaded ahead of the pagination note. Nothing repeats the name or title verbatim.

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

Completeness3/5

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

With no output schema, the description correctly calls out the one return-value detail an agent must act on (nextOffset), which is a real contribution. But for a 0%-covered, deeply nested filter object it leaves most parameters undocumented, and it doesn't hint at what fields the stay results contain, so it is only partially complete.

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 0% on a nested object with 17 filter fields, so the description needs to compensate; it names only location, dates, guests and amenities, omitting bedrooms, bathrooms, sort, propertyType, unitType, searchToken, discountCode, stayLength and the children/infants split. It also explains neither the fixed limit=12 enum nor the offset multipleOf=12 constraint, though the nextOffset note partially clarifies pagination intent.

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 opens with a specific verb+resource ('Search public Hyatus stays') and enumerates the primary dimensions (location, dates, guests, amenities). It implicitly separates itself from get_hyatus_stay and check_hyatus_stay_availability by being the discovery operation, but never names them explicitly.

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 word 'Search' and the 'public ... stays' scope imply this is the entry-point discovery tool, so an agent can infer when to reach for it. However, there is no explicit when-to-use vs. when-not, no stated alternatives, and no mention of what happens if a stay is unavailable (e.g., deferring to availability check).

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.