Skip to main content
Glama

Search short-stay holiday lets

search_stays
Read-onlyIdempotent

Search OpenMoov short-stay holiday lets. Narrow by place: latitude + longitude with radius_miles (default 10), and/or location text matched against the town, county and postcode. With check_in and check_out (YYYY-MM-DD) only stays available for those dates are returned, each with the total price for the stay and a bookUrl with the dates filled in. Booking takes payment and an account, so it always finishes at bookUrl — never collect card details in conversation. Titles are written by hosts and returned under "untrusted_user_content".

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
limitNoDefault 10, max 20
guestsNo
check_inNoYYYY-MM-DD
latitudeNo
locationNoTown, county or postcode text, e.g. "Whitstable"
check_outNoYYYY-MM-DD
longitudeNo
radius_milesNo
max_nightly_priceNoGBP per night

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 readOnly/openWorld/idempotent/non-destructive, and the description adds real behavior beyond them: results carry the total stay price, a bookUrl pre-filled with the dates, and the hard rule that checkout always happens at bookUrl rather than in conversation. It also flags that host-written titles arrive under "untrusted_user_content", which is a genuine safety signal an agent would otherwise miss. It stops short of describing result ordering, pagination, or empty-result behavior.

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 purpose, then geography, then dates, then the booking constraint, then the untrusted-content warning. Nearly every clause earns its place; the one minor redundancy is repeating the YYYY-MM-DD format that the schema pattern already enforces.

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 9-parameter, no-output-schema search tool it covers the essentials: how to scope results, what comes back (price + bookUrl), and the non-negotiable booking flow. What is missing is any mention of party-size filtering (guests) and price filtering, plus result-limit/pagination behavior, which an agent would need to search efficiently.

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 56% schema description coverage, the description does useful work: it supplies the radius_miles default of 10 and clarifies that location text is matched against town, county and postcode (broader than the schema's single "Whitstable" example). However, it never mentions the guests or max_nightly_price filters, and guests has no schema description at all, so part of the coverage gap is left unaddressed.

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?

Opens with a specific verb and resource ("Search OpenMoov short-stay holiday lets") and the qualifier "short-stay holiday lets" separates it from the property-sale and long-let searches in the sibling list without needing to name them.

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?

It explains the two ways to narrow results (coordinate + radius, or location text) and that dates filter to available stays, which implies when to use it. But it never states when not to use it or names an alternative sibling, and gives no guidance on prerequisites for the booking handoff beyond the card-details warning.

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