Skip to main content
Glama

Hotel availability

check_availability
Read-onlyIdempotent

Free nights in the online booking calendar of a hotel deal, for each option: whether a stay of its nights is free from check_in (to check_out when given) and the free nights of the next weeks. Only some hotel deals have a calendar (get_deal: online_booking_calendar); for the others the voucher is booked as its conditions say.

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": {
      "id": "<id>",
      "check_in": "<check_in>"
    },
    "name": "check_availability"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe deal's id.
check_inYesYYYY-MM-DD: arrival.
check_outNoYYYY-MM-DD: departure (optional; default: the option's nights).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already establish readOnlyHint, idempotentHint, non-destructive and closed-world behavior, so the safety profile is covered. The description adds two useful facts beyond that: the response is per-option and includes both stay feasibility from check_in and the free nights of subsequent weeks, and the call is only meaningful for deals with a calendar. It does not say what happens (error vs. empty result) when a deal lacks a calendar, which is the main behavioral ambiguity.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences with no obvious filler, but the first is a dense run-on whose subject and predicate are hard to untangle, and the most decision-relevant fact (only some deals have a calendar) is buried in the second sentence. Front-loading the precondition would improve both scanning and parseability.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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; it partly discharges this by saying results are per option with a free/not-free determination and upcoming free nights. It remains incomplete on the no-calendar case and on the shape of 'options', which leaves the agent guessing about result handling for a non-trivial read.

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 description coverage is 100%, so id, check_in and check_out are already documented, including check_out's default of the option's nights. The description only restates the check_in-to-check_out window and the per-option night default, adding no format, boundary, or interpretation detail beyond the schema. Baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description identifies the resource (a hotel deal's online booking calendar with free-night availability) but opens with a noun phrase rather than a verb, so the operation itself is implied by the tool name rather than stated. The subject matter is specific enough to separate it from siblings like get_deal or search_deals, but the phrasing 'Free nights in the online booking calendar of a hotel deal, for each option' is tangled and takes effort to parse.

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 gives a concrete precondition: only some deals have a calendar, and the agent should check get_deal's online_booking_calendar field to know whether this call applies; otherwise the voucher follows its conditions. This is real when/when-not guidance pointing at a sibling, though it stops short of naming an explicit alternative call to make in the no-calendar case.

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.