Skip to main content
Glama
lumile

LumbreTravel MCP Server

by lumile

create_hotel

Add new hotels to the LumbreTravel system by providing name, description, contact details, and address information for travel program management.

Instructions

Antes de crear un nuevo hotel se debe preguntar al si quiere que primero se busque el hotel a ver si existe.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesNombre del hotel
descriptionYesDescripción del hotel
phoneYesTeléfono del hotel
emailYesEmail del hotel
addressYesDirección del hotel

Implementation Reference

  • MCP tool handler case for 'create_hotel': destructures input arguments, calls apiService.createHotel, and returns the hotel data as formatted text.
    case 'create_hotel': {
      const { name, description, phone, email, address } = args
      const hotel = await this.apiService.createHotel({ name, description, phone, email, address })
      return {
        content: [{ type: 'text', text: JSON.stringify(hotel, null, 2) }]
      }
    }
  • Input schema and description for the 'create_hotel' tool, defining required properties for hotel creation.
      name: 'create_hotel',
      description: 'Antes de crear un nuevo hotel se debe preguntar al si quiere que primero se busque el hotel a ver si existe.',
      inputSchema: {
        type: 'object',
        properties: {
          name: { type: 'string', description: 'Nombre del hotel' },
          description: { type: 'string', description: 'Descripción del hotel' },
          phone: { type: 'string', description: 'Teléfono del hotel' },
          email: { type: 'string', description: 'Email del hotel' },
          address: { type: 'string', description: 'Dirección del hotel' }
        },
        required: ['name', 'description', 'phone', 'email', 'address']
      }
    },
  • Helper service method that performs authenticated POST request to the backend API to create a new hotel.
    async createHotel (data: {
      name: string
      description: string
      phone: string
      email: string
      address: string
    }) {
      const headers = await this.getHeaders()
      const response = await fetch(`${API_CONFIG.baseUrl}/integrations/mcp/hotels/create`, {
        method: 'POST',
        headers: { ...headers, 'Content-Type': 'application/json' },
        body: JSON.stringify(data)
      })
      return await this.handleResponse<any>(response)
    }
  • src/index.ts:38-47 (registration)
    Registers the generic tool handlers (listTools and callTool) on the MCP server, which handle the 'create_hotel' tool via dispatch.
    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 mentions a prerequisite check ('se debe preguntar al si quiere que primero se busque el hotel') but doesn't disclose critical behavioral traits: whether this is a write operation, what permissions are needed, whether duplicates are allowed, what happens on success/failure, or what the response contains. For a creation tool with zero annotation coverage, this is insufficient.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence, which is concise, but it's poorly structured - it starts with a prerequisite instruction rather than stating the tool's purpose. The sentence is somewhat awkwardly phrased and could be more direct about what the tool does.

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?

For a creation tool with 5 required parameters, no annotations, and no output schema, the description is incomplete. It doesn't explain what happens after creation, what validation occurs, whether there are side effects, or what the return value looks like. The focus on a prerequisite check doesn't compensate for missing behavioral context.

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%, so the schema already documents all 5 parameters with clear descriptions. The description adds no parameter information beyond what's in the schema - it doesn't explain relationships between parameters, validation rules, or format requirements. Baseline 3 is appropriate when schema does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states the tool creates a new hotel, which is a clear verb+resource combination. However, it doesn't distinguish this from sibling tools like 'create_agency' or 'create_provider' - all appear to be similar creation operations for different entities. The description focuses more on a prerequisite check than on what the tool actually does.

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 some guidance about checking if a hotel exists first, but doesn't specify when to use this tool versus alternatives like 'update_hotel' or 'get_hotel_by_name'. It mentions a prerequisite action but doesn't provide clear context about when this creation operation is appropriate versus other hotel-related operations.

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