Skip to main content
Glama

Cartas de un hotel

cartas
Read-onlyIdempotent

Enlaces públicos a las cartas (bebidas, snacks, vinos, restaurantes) de un hotel.

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

Input Schema

NameRequiredDescriptionDefault
hotelYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the bar is lower; the description still adds real value by saying the links are 'públicos' and that the payload is links rather than menu content. It does not say what happens when a hotel has no menus or how results are grouped.

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 front-loaded sentence with the resource named first and the category enumeration in parentheses; no filler or redundant restatement of the title.

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

Completeness3/5

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

For a simple, read-only, single-parameter tool with no output schema, the description is close to sufficient but leaves two gaps: the expected format of the hotel identifier and the shape/coverage of the returned links (e.g., missing categories, one link vs. many).

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 0% for the single required 'hotel' parameter, so the description must carry the burden. It only restates that the subject is 'un hotel' and never clarifies the expected identifier form (name, slug, or internal ID), which is the main thing an agent needs to supply.

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 the specific resource (public links to a hotel's menus) and enumerates the covered categories — bebidas, snacks, vinos, restaurantes — so the agent knows exactly what comes back. It does not distinguish itself from nearby informational siblings such as info_hotel or ficha_hotel, so differentiation is left implicit.

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: an agent can infer it should call this when it needs menu/menu-link data for a hotel, but the description never states a when-to-use condition, prerequisites, or an alternative to prefer. No exclusions or fallback guidance are given.

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