Skip to main content
Glama

cancunhotels

Ficha de un hotel

ficha_hotel
Read-only

Ficha resumida de un hotel: ubicación, para quién es, sargazo, pros, contras, lo que no te dicen, distancias y fuentes. Hotel profile summary.

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": "<hotel>"
    },
    "name": "ficha_hotel"
  }
}

Input Schema

NameRequiredDescriptionDefault
hotelYesNombre o slug del hotel (p. ej. 'Excellence Playa Mujeres')
idiomaNoIdioma de la respuesta / response language (default es)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/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 safety profile is covered. The description adds content scope (what the profile contains, including 'lo que no te dicen' and 'fuentes') but says nothing about data freshness, behavior for an unrecognized hotel, or rate limits.

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?

Two short, front-loaded sentences: the Spanish original leads with what the tool returns, followed by a one-line English gloss. The bilingual duplication is mildly redundant but justified by the idioma parameter and costs little.

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 only two well-documented parameters, no output schema, and clear annotations, the description is nearly sufficient; listing the returned sections effectively substitutes for a missing output schema. The only gap is guidance on error/unknown-hotel behavior.

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?

Both parameters carry full schema descriptions (hotel name/slug example, idioma enum with default), so the schema already does the work. The description adds only indirect meaning by hinting at response content sections, not at parameter behavior or edge cases like unknown hotel names.

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 the resource (a single hotel's profile) and enumerates the sections it returns (ubicación, sargazo, pros, contras, distancias, fuentes), which clearly separates it from list/search or comparison siblings. The verb is only implied by 'Ficha'/'profile summary', so it is clear but not stated as a crisp verb+resource pair.

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: the tool clearly serves fetching details for one already-known hotel, while buscar_hoteles and comparar_hoteles cover discovery and comparison. There is no explicit when-to-use/when-not-to-use statement or named alternative in the description, leaving the agent to infer routing.

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