Skip to main content
Glama

Dunn Estates Aspen: The Galena Penthouse

Check availability

check_availability
Read-onlyIdempotent

Night-by-night availability from the live booking calendar between two dates (up to 180 nights). Returns open windows, reserved ranges and whether the whole requested stay is open. Reserved nights are shown simply as reserved. Use get_quote to confirm the price and minimum stay for specific dates.

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": {
      "start": "<start>",
      "end": "<end>"
    },
    "name": "check_availability"
  }
}

Input Schema

NameRequiredDescriptionDefault
endYesMorning after the last night (departure date), YYYY-MM-DD
startYesFirst night to check (arrival date), YYYY-MM-DD

Output Schema

NameRequiredDescriptionDefault
endYes
noteNo
startYes
nightsNo
websiteNo
reservedYes
openWindowsYes
calendarAsOfNo
allNightsOpenYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • removedOutput schema / properties / typicalMinimumNights
      Removed value: -{
      -  "type": "integer"
      -}
  2. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), and the description adds real value beyond them: the 180-night ceiling, the shape of the response (open windows, reserved ranges, whole-stay boolean), and the privacy behavior that reserved nights appear only as 'reserved'. It does not say what happens when the range exceeds 180 nights (error vs. truncation), which is the one behavioral gap.

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?

Three tight sentences, front-loaded with the core purpose, then the return shape, then the alternative-tool routing. No filler or restatement of the tool name.

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?

An output schema exists, so return values need only light mention and the description gives that; the read-only nature is covered by annotations. The remaining omission is behavior at the 180-night boundary and whether reserved-night data includes any detail beyond the 'reserved' label.

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% and the schema already defines start as arrival night and end as the departure morning, so the baseline would be 3. The description adds a constraint not present in the schema — the 180-night maximum span between the two dates — which meaningfully affects valid parameter values.

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 ('Night-by-night availability from the live booking calendar') plus scope ('between two dates, up to 180 nights'), and separates itself from the pricing sibling by routing price questions to get_quote. An agent can distinguish this from get_quote and suggest_dates without opening either 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?

Gives a clear use context (checking whether a specific stay is open) and an explicit alternative for pricing ('Use get_quote to confirm the price and minimum stay'). It does not mention suggest_dates for flexible date selection, nor state when not to call this tool, so the routing picture is helpful but incomplete.

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