Skip to main content
Glama
lumile

LumbreTravel MCP Server

by lumile

update_hotel

Modify hotel details like name, description, contact information, and address in the LumbreTravel system to keep listings current and accurate.

Instructions

Actualizar un hotel

Input Schema

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

Implementation Reference

  • The main handler logic for the 'update_hotel' tool within the callTool switch statement. It extracts arguments, calls the ApiService updateHotel method, and returns the result.
    case 'update_hotel': {
      const { id, name, description, phone, email, address } = args
      const hotel = await this.apiService.updateHotel({ id, name, description, phone, email, address })
      return {
        content: [{ type: 'text', text: JSON.stringify(hotel, null, 2) }]
      }
    }
  • The tool definition including name, description, and input schema in the listTools() method.
    {
      name: 'update_hotel',
      description: 'Actualizar un hotel',
      inputSchema: {
        type: 'object',
        properties: {
          id: { type: 'string', description: 'ID del hotel a actualizar' },
          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: ['id', 'name', 'description', 'phone', 'email', 'address']
      }
    },
  • Supporting ApiService method that sends a PUT request to the external API endpoint to update a hotel.
    async updateHotel (data: {
      id: string
      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/update`, {
        method: 'PUT',
        headers: { ...headers, 'Content-Type': 'application/json' },
        body: JSON.stringify(data)
      })
      return await this.handleResponse<any>(response)
  • src/index.ts:44-47 (registration)
    Server registration of the callTool handler, which dispatches to the specific tool handler based on name.
    this.server.setRequestHandler(
      CallToolRequestSchema,
      async (request) => await this.toolsHandler.callTool(request.params.name, request.params.arguments, this.server)
    )
  • src/index.ts:39-41 (registration)
    Server registration of the listTools handler, which returns the list of available tools including update_hotel.
      ListToolsRequestSchema,
      async () => this.toolsHandler.listTools()
    )
Behavior1/5

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

With no annotations provided, the description carries full burden for behavioral disclosure but provides none. It doesn't indicate this is a mutation operation, mention permission requirements, specify whether updates are partial or complete (all 6 parameters are required), describe error conditions, or explain what happens on success. The single Spanish phrase offers no behavioral context.

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

Conciseness2/5

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

While technically concise with just three words, this represents under-specification rather than effective brevity. The description fails to provide necessary information about a mutation tool with 6 required parameters, making it inefficient for agent understanding despite its short length.

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

Completeness1/5

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

For a mutation tool with 6 required parameters, no annotations, and no output schema, the description is completely inadequate. It provides no behavioral context, no usage guidance, no error information, and minimal purpose clarification. The agent would struggle to use this tool correctly based solely on this description.

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%, with all 6 parameters clearly documented in the input schema. The description adds no parameter information beyond what the schema already provides, so it meets the baseline score of 3 for adequate schema coverage without additional value from the description.

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

Purpose2/5

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

The description 'Actualizar un hotel' (Update a hotel) is a tautology that restates the tool name in Spanish without adding specificity. It doesn't distinguish this tool from sibling update tools like update_agency or update_program, nor does it clarify what aspects of a hotel can be updated beyond what's implied by the name.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided about when to use this tool versus alternatives. The description doesn't mention prerequisites (e.g., needing an existing hotel ID), differentiate from create_hotel for new hotels, or specify when to use update_hotel versus other hotel-related tools like get_hotel_by_name or list_hotels.

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