Skip to main content
Glama

Volotel SkyWay – Cluj-Napoca Airport

Volotel: rooms and prices

check_availability
Read-only

Real-time availability and TOTAL prices (RON) of Volotel SkyWay rooms for the given dates, grouped by room type, plus the direct booking link. Arrival must be tomorrow or later; max 30 nights.

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

Input Schema

NameRequiredDescriptionDefault
guestsNoNumber of guests in one room (1-3)
check_inYesArrival date YYYY-MM-DD
check_outYesDeparture date YYYY-MM-DD

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered; the description adds real behavioral detail beyond them: prices are TOTAL (not per-night) in RON, results are grouped by room type, and the response carries a direct booking link. It does not say how sold-out or partial-availability cases are represented, which keeps it from a 5.

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 with no filler: the first front-loads what the tool returns, the second carries the booking constraints. Every clause earns its place.

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 takes on the job of describing the return payload and does so at a useful level (availability, total prices in RON, grouping, booking link). Remaining gaps are response shape details and edge-case behavior (no availability), which are minor for a read-only lookup.

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%, so the baseline is 3, but the description adds meaning beyond the schema by constraining check_in/check_out (arrival from tomorrow onward, stay capped at 30 nights) and clarifying that guests counts people in one room. That is real semantic value over bare 'YYYY-MM-DD' strings.

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 ('check availability') and a well-scoped resource ('Volotel SkyWay rooms'), plus what comes back: availability, TOTAL prices in RON grouped by room type, and a booking link. Naming the specific property and the price currency separates it from generic siblings like get_property_info.

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?

The description gives concrete preconditions for calling it ('Arrival must be tomorrow or later; max 30 nights'), which acts as clear usage context. It stops short of explicitly routing between this and siblings such as get_property_info, so there are no stated exclusions or alternatives.

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