Skip to main content
Glama

Volotel SkyWay – Cluj-Napoca Airport

Volotel: facts and rules

get_property_info
Read-only

Facts about Volotel SkyWay and Volo House: location, how to get from the airport, check-in/out, rooms, services, breakfast, parking, pets, accessibility, contacts.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_property_info"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safe, closed-domain read profile is covered without the description's help. The description contributes the scope of retrievable facts but says nothing further about behavior — e.g., that it is a static content lookup requiring no auth and no property selector. Adequate but not additive beyond content scope.

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 front-loaded sentence that identifies the subject first, then enumerates topics. The topic list is long but each item earns its place by telling the agent which questions this tool answers; no filler or restatement of the name.

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?

For a zero-parameter, read-only reference tool with annotations covering safety and no output schema, the description covers what an agent needs to know in order to call it. The only residual ambiguity is whether a single call returns facts for both properties or whether results must be disambiguated, which the description leaves unstated.

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?

The tool takes zero parameters and the schema is fully described, so there is nothing for the description to disambiguate at the parameter level. Baseline 4 applies.

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?

"Facts about Volotel SkyWay and Volo House" names the resource precisely and the topic list (location, airport transfers, check-in/out, rooms, breakfast, parking, pets, accessibility) bounds what facts are returned. It does not explicitly contrast itself with the sibling check_volo_house, which by name alone sounds adjacent, so an agent must infer that this is static reference info rather than a per-house lookup.

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 by the enumerated topics: an agent can infer "use this for policy/logistics questions about the properties." There is no explicit when-to-use statement, no exclusion such as "do not use for availability or rates — use check_availability," and no mention of which sibling to prefer for house-specific queries.

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