Open and booked nights for Wanaka Haus (sleeps 8, Wānaka NZ) in a date window, up to 18 months ahead. Ranges are check-in inclusive, check-out exclusive.
| Name | Required | Description | Default |
|---|---|---|---|
| to | No | Window end, YYYY-MM-DD. Defaults to 18 months out. | |
| from | No | Window start, YYYY-MM-DD. Defaults to today. |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden. It discloses the date window constraint (up to 18 months) and clarifies the inclusive/exclusive boundary for check-in/check-out. It does not mention whether the tool is read-only or has any side effects, but the content strongly implies a safe query operation.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is two sentences without any filler. It front-loads the core purpose and follows with a critical clarification. Every sentence serves a purpose.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given no output schema, the description does not detail return format. However, it does state it returns 'open and booked nights', which is sufficient for a simple availability lookup. It could mention maximum range or pagination but is reasonably complete for the complexity level.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100%, so baseline is 3. The description adds significant value by clarifying that ranges are 'check-in inclusive, check-out exclusive', which is not obvious from the schema alone. It also confirms the defaults (today and 18 months out) that are already in the schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description explicitly states the tool retrieves 'open and booked nights' for a specific property ('Wanaka Haus') within a date window, up to 18 months ahead. This clearly distinguishes it from sibling tools (cancel_booking, create_booking, etc.) which manage bookings rather than querying availability.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies usage for checking availability before creating a booking. While it doesn't explicitly state when not to use it or name alternatives, the context and sibling tool names make the intended use clear. It could benefit from an explicit note, but it's adequate.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool has a clearly distinct purpose: searching availability, getting a quote, creating a booking, checking booking status, and canceling. No overlap or ambiguity.
All tool names follow a consistent verb_noun pattern in snake_case (e.g., search_availability, create_booking, cancel_booking), making them predictable and easy to understand.
With 5 tools covering the core booking workflow (search, quote, create, status, cancel), the count is well-scoped and appropriate for the server's purpose.
The tool surface covers the essential lifecycle of a booking: checking availability, pricing, creation, status retrieval, and cancellation. No obvious gaps for typical booking operations.