Skip to main content
Glama

Search stays

search_stays
Read-only

Searches vacation rentals that are free for the given dates in a place and returns homes with their all-in totals (fees and taxes included), cheapest first, with links and offer_ids for get_quote. For trips without a specific listing in mind.

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": {
      "location": "<location>",
      "check_in": "<check_in>",
      "check_out": "<check_out>",
      "adults": "<adults>"
    },
    "name": "search_stays"
  }
}

Input Schema

NameRequiredDescriptionDefault
petsNoPets (service animals don't count). Default 0
limitNoHow many results to return, 1-20. Default 10
adultsYesGuests aged 13 or older
infantsNoGuests under 2; they don't count toward capacity. Default 0
check_inYesCheck-in date, YYYY-MM-DD
childrenNoGuests aged 2-12. Default 0
locationYesWhere to stay: a city, region or neighborhood, e.g. "Lisbon" or "Joshua Tree, California"
check_outYesCheck-out date (the morning the traveler leaves), YYYY-MM-DD
max_totalNoOnly stays whose all-in total (USD) is at most this
min_bedroomsNoOnly homes with at least this many bedrooms

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations only say readOnly and openWorld; the description adds real behavior by declaring that prices are all-in totals with fees and taxes, that results are sorted cheapest first, and that each home carries links and offer_ids. It stops short of covering empty/no-availability results or the limit behavior.

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?

One sentence, front-loaded with the core action and scope, then the return shape and the intended trip type. No filler, no repetition of schema fields.

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 10 parameters and no output schema, the description supplies the essential return shape (homes, all-in totals, ordering, links, offer_ids) so the agent knows what comes back and how to chain to get_quote. Missing only edge behavior such as no availability or how limit interacts with results.

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 coverage is 100%, so every parameter is already documented, including max_total's all-in USD semantics and location examples. The description adds only the framing that dates must be 'free' for the stay, nothing beyond schema on the 10 parameters.

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?

States a specific verb+resource ('Searches vacation rentals') plus scope: free for the given dates in a place, all-in totals, cheapest-first ordering, and offer_ids for get_quote. An agent can distinguish it from get_quote and book without opening any schema.

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?

'For trips without a specific listing in mind' clearly sets the condition that separates this discovery path from the quote path. It routes to get_quote via offer_ids, but never mentions find_cheaper or book, and offers no exclusion guidance for other cases.

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