Skip to main content
Glama

Volotel SkyWay – Cluj-Napoca Airport

Volo House: entire house

check_volo_house
Read-only

Whether Volo House (separate entire house next to Volotel, 2 bedrooms + sofa bed, 2 bathrooms, kitchen, up to 6 guests) is free for the given dates, the price and how to book (online up to 4 guests).

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_volo_house"
  }
}

Input Schema

NameRequiredDescriptionDefault
guestsNoNumber of guests (adults + children), 1-6
check_inYesArrival date YYYY-MM-DD
check_outYesDeparture date YYYY-MM-DD

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/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. Beyond that, the description adds genuinely useful behavioural context the annotations do not: the house sleeps up to 6 but online booking only supports up to 4 guests, which tells the agent when to escalate rather than send the user to the booking flow. It does not describe failure behaviour for invalid date ranges or fully booked dates, which keeps it below 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.

Conciseness4/5

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

One sentence, front-loaded with the core question (is it free for these dates) followed by the secondary outputs (price, how to book). The parenthetical property facts are dense but informative rather than wasteful. Slightly awkward phrasing ('Whether ... is free ... the price and how to book') costs it a point.

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?

There is no output schema, so the description must carry the return shape, and it does: availability, price, and booking instructions. Combined with the 100%-covered schema and read-only annotations, an agent has what it needs to call this tool correctly. Only edge-case behaviour (sold-out dates, >4-guest booking path) is left unstated.

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 check_in, check_out and guests are already fully documented in the schema. The description only echoes the capacity ('up to 6 guests') and date-range framing, adding no new syntax, format, or default semantics. Baseline 3 is correct when the schema does the heavy lifting.

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 (Volo House, the separate entire house next to Volotel) and specific verbs: check availability for given dates, return the price, and explain how to book. That is far more than a restatement of the name. It does not explicitly contrast itself with the sibling tools check_availability or get_property_info, so it stops short of a 5.

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?

Usage is only implied: an agent can infer this is the tool for whole-house Volo House enquiries because of the 'given dates' and 'how to book' framing. There is no explicit statement of when to prefer this over check_availability, nor any exclusion or prerequisite. Adequate but leaves routing to inference.

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