Skip to main content
Glama

Guest2Host

Search vacation rentals

search_stays
Read-onlyIdempotent

Find vacation rentals listed by their owners that are booked directly on the owner's own website (no platform fees). Filter by place, dates, guests, pets and nightly price. With checkIn and checkOut, only stays open for those dates are returned. Returns up to 25 stays with photo, price, owner-reported rating and booking link.

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_stays"
  }
}

Input Schema

NameRequiredDescriptionDefault
petsNotrue = only stays that allow pets
limitNoMaximum results (default 10)
whereNoTown, state, region or kind of place, e.g. "McMinnville", "Oregon wine country", "lake Alabama"
guestsNoNumber of guests the stay must sleep
checkInNoCheck-in date, YYYY-MM-DD
checkOutNoCheck-out date, YYYY-MM-DD
maxPricePerNightNoHighest acceptable "from" nightly rate, USD

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare this is a safe, idempotent, non-destructive read operation. The description adds useful behavioral context: direct-owner listings, no platform fees, date-availability filtering, a 25-result cap, and the returned fields. It does not discuss auth or rate limits, but those are not central for a search tool.

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?

Three tight sentences with the core purpose front-loaded, followed by filters and return behavior. No obvious filler, though it could be slightly more scannable.

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 seven-parameter search tool with no output schema, the description covers purpose, key filters, availability semantics, result cap, and returned fields. Minor omissions such as result ordering are not significant here.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3. The description adds meaning by explaining that checkIn/checkOut returns only stays open for those dates and by summarizing what pets, guests, price, and place filters do.

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 and resource: find vacation rentals listed by owners and booked directly on the owner's website. The no-platform-fees framing and filtering scope make it clearly distinguishable from siblings such as get_stay or check_dates.

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?

Gives clear context for filtering by place, dates, guests, pets, and price, and explains the checkIn/checkOut behavior. It does not explicitly say when to use this versus alternatives like check_dates or get_stay, so guidance is implied rather than complete.

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