Skip to main content
Glama
lumile

LumbreTravel MCP Server

by lumile

list_hotels

Retrieve available hotels to associate with activities in travel programs using the LumbreTravel MCP Server.

Instructions

Obtiene todos los hoteles disponibles para asociar a una actividad en un programa de viajes

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function for the 'list_hotels' tool. It calls apiService.getHotels() to retrieve the list of hotels and returns the JSON-stringified response as text content.
    case 'list_hotels': {
      const hotels = await this.apiService.getHotels()
      return {
        content: [{
          type: 'text',
          text: JSON.stringify(hotels, null, 2)
        }]
      }
    }
  • The schema definition for the 'list_hotels' tool, including name, description, and empty input schema (no parameters required).
      name: 'list_hotels',
      description: 'Obtiene todos los hoteles disponibles para asociar a una actividad en un programa de viajes',
      inputSchema: {
        type: 'object',
        properties: {}
      }
    },
  • Helper method getHotels() in ApiService that performs the actual HTTP GET request to fetch the list of hotels from the backend API.
    async getHotels () {
      const headers = await this.getHeaders()
      const response = await fetch(`${API_CONFIG.baseUrl}/integrations/mcp/hotels`, {
        method: 'GET',
        headers
      })
      return await this.handleResponse<any[]>(response)
    }
  • src/index.ts:38-47 (registration)
    Registration of the tool handlers on the MCP server: ListToolsRequestSchema maps to listTools() (which includes 'list_hotels' schema), and CallToolRequestSchema maps to callTool() (which dispatches to the specific handler).
    this.server.setRequestHandler(
      ListToolsRequestSchema,
      async () => this.toolsHandler.listTools()
    )
    
    // Configure handlers for tools
    this.server.setRequestHandler(
      CallToolRequestSchema,
      async (request) => await this.toolsHandler.callTool(request.params.name, request.params.arguments, this.server)
    )
Behavior2/5

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

No annotations are provided, so the description carries full burden. It describes a read operation ('obtiene') but doesn't disclose important behavioral traits: whether this returns all hotels or paginated results, what 'disponibles' means operationally (e.g., active vs inactive), authentication requirements, rate limits, or response format. For a list operation with zero annotation coverage, this leaves significant gaps in understanding how the tool behaves.

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?

The description is a single, efficient Spanish sentence that communicates the core purpose and context without unnecessary words. It's appropriately sized for a simple list tool and front-loads the essential information ('Obtiene todos los hoteles disponibles'). Every part of the sentence contributes meaning.

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 zero-parameter list tool with no output schema, the description provides adequate basic context about what it retrieves and why. However, without annotations covering behavioral aspects and no output schema to describe return values, the description should ideally mention what information is returned about hotels and any limitations. It's minimally viable but leaves gaps in understanding the full operation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has 0 parameters with 100% schema description coverage (empty schema). The description appropriately doesn't discuss parameters since none exist. It earns a baseline 4 because when there are no parameters, the description needn't compensate for schema gaps, and it correctly focuses on the tool's purpose rather than parameter details.

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 verb ('obtiene' - gets/retrieves) and resource ('hoteles disponibles' - available hotels) with specific context ('para asociar a una actividad en un programa de viajes' - to associate with an activity in a travel program). It distinguishes from obvious siblings like 'create_hotel' or 'get_hotel_by_name' by indicating it retrieves all available hotels rather than creating or filtering by name. However, it doesn't explicitly differentiate from other list tools like 'list_agencies' or 'list_services' beyond the resource type.

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?

The description implies usage context ('para asociar a una actividad en un programa de viajes') suggesting this tool is used when needing hotels to associate with travel activities. However, it doesn't provide explicit guidance on when to use this versus alternatives like 'get_hotel_by_name' for specific lookups or 'create_hotel' for adding new hotels. No exclusion criteria or prerequisites are mentioned.

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