Skip to main content
Glama
Sign In

Cancun4me — Reservas de Hotel

by me.cancun4
OverviewDiscussionsAdmin

list_hotels

Lista o catalogo curado de hoteis do Cancun4me (nome, zona, descricao, destaques, fotos), sem precisar de datas ou chave pessoal. Bom para descobrir/descrever hoteis antes de o hospede escolher datas. language: 'en', 'pt' ou 'es'.

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

Input Schema

NameRequiredDescriptionDefault
languageNoen

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior3/5

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

With no annotations, the description carries the transparency burden. It discloses that no dates or personal key are required (no auth) and that it returns a curated catalog. It does not explain return size, pagination, or potential errors, but for a simple list, this is acceptable.

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?

The description is a single, well-structured sentence that front-loads the action and includes all necessary details without redundancy.

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?

The tool is simple (one optional param, no output schema). The description covers the content, use case, and language values. It does not explicitly differentiate from sibling search_hotels, but the 'no dates' comment implicitly does. Adequate.

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

Parameters5/5

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

The schema only provides a default for 'language' with no enum or description. The description adds the allowed values ('en', 'pt', or 'es') and implies localization, fully compensating for the schema's lack of detail.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool lists the curated hotel catalog with specific fields (name, zone, description, highlights, photos) and explicitly notes it does not require dates or personal key, distinguishing it from search/filtering tools.

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

Usage Guidelines4/5

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

The description provides a clear use case: discovering/describing hotels before the guest chooses dates. It mentions no dates or personal key are needed, implying when this tool is appropriate. However, it does not explicitly name sibling tools or state when not to use it.

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

All Cancun4me — Reservas de Hotel toolsInspect
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