Skip to main content
Glama

Información de un hotel

info_hotel
Read-onlyIdempotent

Preguntas y respuestas confirmadas de un hotel. Sin tema, devuelve todas; con tema (p. ej. restaurants), solo ese.

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

Input Schema

NameRequiredDescriptionDefault
temaNoTema opcional, tal como lo devuelve ficha_hotel
hotelYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds one useful behavioural fact — only confirmed Q&A are returned, and the default scope is everything — but says nothing about result volume, pagination or what a topic value looks like beyond one example.

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?

Two short clauses, no filler, and the default-versus-filter rule is front-loaded. Nothing could be removed without losing information.

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?

For a two-parameter read-only lookup with no output schema and rich annotations, the description covers the core contract adequately. The main residual gap is how a hotel is identified, which matters because that parameter is required and undocumented.

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?

With 50% schema coverage, only tema carries a schema description, and the description usefully extends it with the default semantics and an example ('restaurants'). The mandatory hotel parameter is undocumented in both schema and description (name vs. identifier), leaving half the input contract unexplained.

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 a specific resource — confirmed Q&A (preguntas y respuestas confirmadas) for a hotel — and explains the filtering behaviour, so an agent knows what it retrieves. The verb is implicit rather than stated and nothing distinguishes it explicitly from siblings such as ficha_hotel, keeping it out of the top band.

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?

It gives a clear conditional instruction for the optional parameter (omit tema = all topics, supply tema = that single topic), which is genuine usage guidance. However, there is no stated condition for choosing this tool over ficha_hotel, info_cadena or cartas for hotel information, so the agent must infer the boundary.

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