Corissia Resorts Crete

Facts of all five hotels

get_facts_all_hotels

Read-onlyIdempotent

One category of facts at all five hotels in one answer: the facts the same at every hotel once (same_in_all_hotels, id all.), the others hotel by hotel (differ: null where a hotel has no such fact; "unknown, ask the hotel" where the hotel has not confirmed it). Dining and room facts are by hotel. API v3.

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": {
      "category": "<category>"
    },
    "name": "get_facts_all_hotels"
  }
}

Input Schema

Name	Required	Description	Default
`lang`	No	Language of names, texts and links: de or en (default en).
`category`	Yes	The category: identity, operation, policies, location, pools, services, accessibility, terms, sales.

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 9, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare read-only, idempotent, open-world and non-destructive behavior, so the bar is lower. The description goes beyond them by disclosing the response semantics: common facts collapsed once under same_in_all_hotels with id all.<key>, divergent facts listed per hotel, and explicit sentinel values (null vs 'unknown, ask the hotel'), which is genuinely useful context an agent cannot get from the annotations.

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?

A single densely packed sentence that front-loads the purpose and then explains output shape. Every clause (same-facts collapse, differ handling, sentinels, per-hotel dining/rooms, API version) carries distinct information with no filler.

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 burden of explaining returns and does so reasonably: the same_in_all_hotels container, the all.<key> id convention, per-hotel divergence, and the two sentinel values. Minor gaps remain (exact shape of the 'differ' structure, pagination/size limits) but nothing critical for calling the tool correctly.

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% and both parameters are fully described with enums, so the schema does the heavy lifting. The description only implies the category parameter via 'One category of facts' and adds no meaning about the lang parameter or the nine category values.

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 states a specific verb+resource+scope: one category of facts returned for all five hotels in a single answer. That clearly distinguishes it from a single-hotel facts lookup, though it never names the sibling tool it replaces (e.g. get_hotel_facts).

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 implied rather than stated: 'all five hotels in one answer' signals the batch/aggregate use case, and 'Dining and room facts are by hotel' hints at a per-hotel alternative. There is no explicit when-to-use or when-not-to-use guidance and no named alternative such as compare_hotels or get_hotel_facts.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Corissia Resorts Crete tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?