Skip to main content
Glama

Check availability

check_availability
Read-onlyIdempotent

Open start times and prices for an hourly hotel on a date within the next 13 days, grouped by length of stay (2, 3, 6 hours or overnight). For other venues it returns the booking page, which shows open times.

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": {
      "venue_id": "<venue_id>",
      "date": "<date>"
    },
    "name": "check_availability"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateYesDate as YYYY-MM-DD (Hong Kong time).
languageNoResult language: "zh" (default) or "en".
venue_idYesA venue_id from search_venues, such as "venue:my-party-room" or "hotel:my-hotel".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare a read-only, non-destructive, idempotent call, so the safety profile is covered. The description adds real behavior beyond that: the 13-day date window, the 2/3/6-hour or overnight stay grouping, and the fact that non-hourly-hotel venues return a booking page rather than structured times.

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: the primary behavior first, the exception for other venues second. No filler or restated title.

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 no output schema, the description carries the burden of explaining returns, and it does so reasonably: grouped availability and prices for hourly hotels, a booking page otherwise. It could say more about the shape of the booking-page result, but an agent can call this correctly from what is written.

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 all three parameters are already documented with formats, defaults, and a valid id example. The description only contributes the additional constraint that the date must fall within the next 13 days; it adds nothing about the language parameter or the venue type distinction.

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 a specific resource (open start times and prices) and scopes it to hourly hotels, plus explains the fallback for other venues. It is clearly distinct from get_venue_details and search_venues, though it never names those siblings explicitly to route the agent.

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?

The 13-day booking window is stated, which implicitly tells the agent when this tool is valid, and the venue_id schema note points back to search_venues. But there is no explicit 'use this instead of X when Y' guidance and no statement of when-not to call it.

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