Skip to main content
Glama

Ficha de un hotel

ficha_hotel
Read-onlyIdempotent

Datos generales de un hotel (categoría, contacto, periodo de apertura…) y los temas de información que tiene.

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
hotelYesIdentificador (slug) o nombre del hotel

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered without the description. The description adds that the response bundles 'temas de información' alongside the general data, which hints at the payload shape, but it says nothing about whether an unknown hotel produces an error or empty result.

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?

One front-loaded sentence that names the resource first and then the returned content, with no filler. The trailing ellipsis leaves the field list slightly open-ended but does not waste words.

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 one-parameter read-only tool this is close to adequate: it says what data comes back. With no output schema, though, the vague 'temas de información' is never explained, and the overlap with info_hotel leaves an agent guessing which to call.

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?

Schema description coverage is 100% and the single 'hotel' parameter is already documented in the schema as a slug or name. The description adds no further meaning, such as accepted name formats or matching behavior, so the baseline of 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 clear resource (hotel) and enumerates the content returned (categoría, contacto, periodo de apertura) plus 'temas de información', so an agent knows this is an overview/ficha lookup. It does not, however, differentiate itself from the sibling 'info_hotel', which by name appears to cover very similar ground.

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 guidance at all: no statement of when to pick ficha_hotel over info_hotel, buscar, listar_hoteles or comparar_hoteles, and no prerequisites. Usage is only inferable from the name and the field list.

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