Skip to main content
Glama

Check stay dates

check_availability
Read-onlyIdempotent

Check whether the house is open for checkIn, checkOut, and guests. petCount defaults to 0. A blocked stay returns unavailableReason booked. A stay shorter than the check-in minimum returns below_min_stay, minStayNights, and a suggestion. The minimum is looked up even when the 10-minute price cache is empty. Dates are not reserved. This response does not include a price.

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": {
      "checkIn": "<checkIn>",
      "checkOut": "<checkOut>",
      "guests": "<guests>"
    },
    "name": "check_availability"
  }
}

Input Schema

NameRequiredDescriptionDefault
guestsYesRegistered guests, 1 to 10.
checkInYesCheck-in date as YYYY-MM-DD in America/Los_Angeles.
checkOutYesCheck-out date as YYYY-MM-DD. Exclusive.
petCountNoDogs or cats, 0 to 2. Defaults to 0 when omitted.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • removedInput schema / additionalProperties
      Removed value: -false
  2. First observed

TDQS

A3.8/5.0
Behavior5/5

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

Goes well past the annotations (which only cover read-only/idempotent safety) by disclosing the failure modes and their payloads: unavailableReason 'booked', 'below_min_stay' with minStayNights plus a suggestion, and that the minimum is looked up even on an empty 10-minute price cache. It also explicitly states dates are not reserved, which is the key behavioral caveat for a check 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?

Front-loaded with the core purpose and built from short, information-dense sentences with no filler. The telegraphic fragments ('A blocked stay returns unavailableReason booked.') are efficient, though a slightly more grouped structure would read better.

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 carries the full burden of describing the return value. It documents the negative outcomes well but never says what a successful, available response contains beyond the fact that it lacks a price, leaving the agent to discover the success shape at call time.

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 100%, so checkIn/checkOut/guests/petCount semantics are already fully documented, including the petCount default and the LA timezone. The description's 'petCount defaults to 0' merely repeats the schema, adding no new meaning.

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 ('Check whether the house is open for checkIn, checkOut, and guests') with clear scope. It also carves itself away from the pricing siblings by declaring 'This response does not include a price,' though it never names get_quote or get_booking_link directly.

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?

Usage is only implied: the 'no price' note and 'Dates are not reserved' hint that this is a pre-booking feasibility check that precedes get_quote. There is no explicit when-to-use / when-not-to-use statement or named alternative, leaving the agent to infer the sequence.

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