Skip to main content
Glama

cancunhotels

Guías y comparativas

listar_guias
Read-only

Lista las páginas comparativas y categorías del sitio (solo adultos, Playa Mujeres, Riu, cerca del aeropuerto, menos sargazo...). Lists comparison guides.

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": "listar_guias"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/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 by structured data. The description adds useful scope information about what kind of pages are enumerated (adult-only, Playa Mujeres, Riu, airport proximity, low sargazo), but says nothing about return shape, ordering, or pagination even though it is a listing tool.

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?

The resource is named first, followed by concrete examples, which is well front-loaded and compact. The trailing English sentence "Lists comparison guides" is largely redundant with the Spanish text, but it does confirm bilingual intent at minimal cost.

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

Completeness5/5

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

For a zero-required-parameter, read-only listing tool with no output schema, the description gives enough to know the resource and the kind of content returned. Annotations already carry the safety profile, so nothing essential is missing for correct invocation.

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?

There is a single parameter and schema coverage is 100%, with the enum es/en and its default already documented in the schema. The description adds no further detail about the language parameter or its effect on the listed page names, so the baseline 3 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?

States a specific verb ("Lista") and a concrete resource ("páginas comparativas y categorías del sitio"), and the parenthetical examples (solo adultos, Playa Mujeres, Riu, cerca del aeropuerto, menos sargazo) make clear this is an index of site guide pages rather than a hotel search. It does not explicitly name a sibling such as comparar_hoteles or buscar_hoteles to draw the boundary, which keeps it at 4 rather than 5.

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 when-to-use or when-not-to-use guidance, and no alternative is mentioned. An agent can only infer usage from the phrase "páginas comparativas y categorías del sitio", leaving open whether to call this or comparar_hoteles when the user asks for comparisons.

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