Skip to main content
Glama

Dunn Estates Aspen: The Galena Penthouse

Suggest open dates

suggest_dates
Read-onlyIdempotent

Lists open stay windows in a given month that fit the requested length, with live all-in totals for the first few. Use it when the guest is flexible ("a long weekend in February").

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": {
      "month": "<month>"
    },
    "name": "suggest_dates"
  }
}

Input Schema

NameRequiredDescriptionDefault
monthYesMonth to search, YYYY-MM
guestsNoNumber of guests
nightsNoLength of stay in nights

Output Schema

NameRequiredDescriptionDefault
noteNo
monthYes
nightsNo
noticeNo
windowsYes

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/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely new behavior: results include live all-in totals, but only for "the first few" windows, warning the agent that not every listed window is priced. It stops short of explaining ordering or how many results come back.

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?

Two tight sentences: what it returns first, when to use it second. No filler, no restating the title, and the most decision-relevant information leads.

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?

With an output schema present, return values need no explanation, and the description covers scope, pricing behavior and the flexible-date trigger. The only unaddressed item is the unusual guests cap of 2, which an agent might otherwise find surprising.

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 coverage is 100%, so month, guests and nights are already documented with format and bounds. The description only loosely restates the nights parameter as "requested length" and says nothing about the notable guests maximum of 2, so it adds little beyond the schema.

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 gives a specific verb and resource ("Lists open stay windows in a given month that fit the requested length") plus the extra detail that results include live all-in totals. That is clearly distinguishable from a point-availability check like check_availability, though it never names the sibling explicitly.

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?

It states a clear usage condition with a concrete example: "Use it when the guest is flexible ('a long weekend in February')". That tells the agent the flexible-date scenario, but it does not state when-not to use it or name check_availability/get_quote as the alternative for fixed dates.

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