Skip to main content
Glama
lumile

LumbreTravel MCP Server

by lumile

get_hotel_by_name

Search for hotels by name using the LumbreTravel MCP Server to retrieve a list of matching accommodations.

Instructions

Buscar hoteles por su nombre, retorna la lista de hoteles encontrados.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesNombre del hotel

Implementation Reference

  • Registration of the 'get_hotel_by_name' tool including its name, description, and input schema.
    {
      name: 'get_hotel_by_name',
      description: 'Buscar hoteles por su nombre, retorna la lista de hoteles encontrados.',
      inputSchema: {
        type: 'object',
        properties: { name: { type: 'string', description: 'Nombre del hotel' } },
        required: ['name']
      }
    },
  • Handler logic in callTool method that extracts the 'name' argument, calls apiService.getHotelByName, and returns the result as formatted JSON text.
    case 'get_hotel_by_name': {
      const { name } = args as { name: string }
      const hotel = await this.apiService.getHotelByName(name)
      return {
        content: [{ type: 'text', text: JSON.stringify(hotel, null, 2) }]
      }
    }
  • Helper method in ApiService that makes a POST request to the backend API endpoint '/integrations/mcp/hotels/get_hotels_by_name' with the hotel name to retrieve matching hotels.
    async getHotelByName (name: string) {
      const headers = await this.getHeaders()
      const response = await fetch(`${API_CONFIG.baseUrl}/integrations/mcp/hotels/get_hotels_by_name`, {
        method: 'POST',
        headers: { ...headers, 'Content-Type': 'application/json' },
        body: JSON.stringify({ name })
      })
      return await this.handleResponse<any>(response)
    }
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions the action (search by name) and output (list of hotels found), but lacks details on permissions, rate limits, pagination, error handling, or what constitutes a 'found' hotel (e.g., exact match, partial match). For a read operation with zero annotation coverage, this is a significant gap in transparency.

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?

The description is concise and front-loaded, consisting of one sentence that states the purpose and output. There is no wasted text, but it could be slightly more structured by separating purpose from output details. It efficiently conveys the core function without redundancy.

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

Completeness2/5

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

Given the complexity (a search tool with no annotations and no output schema), the description is incomplete. It lacks details on behavioral traits, output format (e.g., structure of the hotel list), error cases, and differentiation from siblings. For a tool that returns data, more context is needed to guide effective use, especially without annotations or output schema.

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?

The description adds minimal semantic value beyond the input schema. It implies the 'name' parameter is used for searching, but the schema already has 100% coverage with a clear description ('Nombre del hotel'). No additional details on format, constraints, or search behavior (e.g., case sensitivity) are provided. With high schema coverage, the baseline is 3, as the description does not compensate with extra insights.

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 clearly states the tool's purpose: 'Buscar hoteles por su nombre' (Search hotels by their name) and 'retorna la lista de hoteles encontrados' (returns the list of hotels found). It specifies the verb (search/retrieve) and resource (hotels), but does not explicitly differentiate it from sibling tools like 'list_hotels' or other 'get_by_name' tools, which would require a 5.

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?

The description provides no guidance on when to use this tool versus alternatives. It does not mention sibling tools such as 'list_hotels' (which might list all hotels without filtering) or other 'get_by_name' tools for different resources, nor does it specify prerequisites or exclusions. Usage is implied by the name and description but not explicitly stated.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/lumile/lumbretravel-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server