Skip to main content
Glama

cancunhotels

Comparar dos hoteles

comparar_hoteles
Read-only

Compara dos hoteles lado a lado. Compare two hotels side by side.

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": {
      "hotel_a": "<hotel_a>",
      "hotel_b": "<hotel_b>"
    },
    "name": "comparar_hoteles"
  }
}

Input Schema

NameRequiredDescriptionDefault
idiomaNoIdioma de la respuesta / response language (default es)
hotel_aYes
hotel_bYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.4/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. Beyond that the description adds nothing: it does not say what dimensions are compared, what the comparison output looks like, or how missing/unknown hotels are handled.

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?

It is short and front-loaded, so nothing is bloated. But the bilingual duplication conveys no additional information, and the brevity comes at the cost of under-specification rather than efficiency.

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

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with no output schema and two undocumented required parameters, the description should carry more weight than one sentence. An agent cannot tell what to pass for hotel_a/hotel_b or what a successful comparison returns.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 33% — only 'idioma' is documented (enum es/en with a default). The critical parameters hotel_a and hotel_b are bare strings with no description, and the description does not clarify whether they expect a name, slug, or ID, which is a real ambiguity given the buscar_hoteles/ficha_hotel siblings.

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 gives a recognizable verb+resource (compare two hotels) and 'lado a lado / side by side' hints that the result is a side-by-side comparison rather than a listing. However, it largely restates the tool name 'comparar_hoteles' and the title 'Comparar dos hoteles', and it never distinguishes the tool from siblings like ficha_hotel, which an agent could equally use to inspect individual hotels.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit when-to-use or when-not-to-use guidance, and no mention of the alternatives (ficha_hotel for single-hotel detail, buscar_hoteles for discovery). Only a weak implication exists that this tool is for two-hotel comparison.

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