Skip to main content
Glama

Happy Island Cottage booking

Check availability

check_availability
Read-only

Booked date ranges and open windows for the three homes, from the live calendars (refreshed every 30 minutes). Ranges are start to end with end exclusive: a checkout day is open for a new check in. openWindows lists every gap at least as long as that home's minimum stay inside the window you ask for (default today plus 180 days, longest 400). A window flagged clippedAtWindowEnd may continue past your 'to' date. Homes: Happy Island Cottage (happy-island-cottage, sleeps 6, 7 night minimum); Happy Turtle A (happy-turtle-a, sleeps 5, 3 night minimum); Happy Turtle B (happy-turtle-b, sleeps 4, 3 night minimum).

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": "check_availability"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoLast day, exclusive, YYYY-MM-DD (default from plus 180 days)
fromNoFirst day to look at, YYYY-MM-DD (default today)
propertyNohappy-island-cottage = Happy Island Cottage, sleeps 6; happy-turtle-a = Happy Turtle A, sleeps 5; happy-turtle-b = Happy Turtle B, sleeps 4

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior5/5

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

Annotations already establish a safe read (readOnlyHint=true, destructiveHint=false, openWorldHint=false), and the description adds substantial context on top: 30-minute calendar refresh cadence, end-exclusive range semantics ('a checkout day is open for a new check in'), minimum-stay filtering of openWindows, the 400-day window cap, and the clippedAtWindowEnd caveat. These are exactly the behavioral traits an agent needs to interpret results correctly.

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?

The lead sentence is front-loaded with what the tool returns, followed by semantics, then a compact home roster. It is dense but nearly every clause carries operational meaning; the sleep-capacity figures duplicate the schema enum slightly, which is minor waste.

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?

There is no output schema, so the description carries the return-value burden, and it does explain bookedRanges, openWindows, and the clippedAtWindowEnd flag. The internal field structure of booked range or window entries is still unspecified, but an agent can call it and read results correctly.

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; however the description adds real meaning beyond the schema by explaining that 'to' is exclusive and why, that defaults are today and today+180, and hard cap of 400 days. It also restates the per-home minimum stay, which the enum description omits.

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 names the exact resource returned: booked date ranges and open windows for three named homes, sourced from live calendars. It is highly specific about the data model (booked ranges vs. open windows, end-exclusive boundaries). It does not explicitly contrast with the sibling tools get_quote or request_booking, which keeps it from a 5.

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 context is implied through the default window (today plus 180 days, max 400) and the minimum-stay filtering rule, which tells an agent how to frame a query. There is no explicit when-to-use-this-vs-get_quote guidance, no statement of prerequisites, and no exclusions. It is adequate but leaves the routing decision to inference.

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