Skip to main content
Glama

Buscar en la información de los hoteles

buscar
Read-onlyIdempotent

Busca un texto en las preguntas y respuestas confirmadas. Con hotel, solo en ese; sin hotel, en todos los que tengas asignados (los resultados indican el 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": {
      "texto": "<texto>"
    },
    "name": "buscar"
  }
}

Input Schema

NameRequiredDescriptionDefault
hotelNo
textoYes
limiteNo

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 readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description usefully adds that results carry the hotel identifier when searching across all assigned hotels, but says nothing about the cap on returned items, ordering, or matching behavior (exact vs partial text).

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?

Two tight sentences that front-load the action and then the scoping rule; no filler. It could earn a 5 only by also covering the undocumented 'limite' behavior in the same compact form.

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?

Adequate for a simple three-parameter read-only search with no output schema: the agent knows what is searched and how scope works. It leaves the result-limit parameter and the shape of returned matches underspecified, which matters for a search tool.

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 0%, so the description must carry the load. It clarifies the meaning of 'hotel' as a scope filter and implies 'texto' is the search string, but 'limite' goes entirely unexplained — neither its default nor that it caps at 25 results.

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 ('Busca') and a clearly bounded resource ('preguntas y respuestas confirmadas'), which distinguishes it from the listing and comparison siblings. It stops short of naming any alternative tool by name.

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?

Explains the conditional scoping rule well (with 'hotel' the search is restricted to that property; without it, it spans all assigned hotels), which is the main usage decision. It gives no when-not-to-use guidance and does not point to siblings such as ficha_hotel or info_hotel when the user wants full hotel detail rather than Q&A text.

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