Skip to main content
Glama
lumile

LumbreTravel MCP Server

by lumile

reactivate_hotel

Reactivate a deactivated hotel in the LumbreTravel system by providing its unique ID to restore availability for bookings and management.

Instructions

Reactivar un hotel

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesID del hotel a reactivar

Implementation Reference

  • The execution handler for the 'reactivate_hotel' tool within the callTool switch statement. It destructures the 'id' from arguments and calls the ApiService's reactivateHotel method.
    case 'reactivate_hotel': {
      const { id } = args as { id: string }
      const hotel = await this.apiService.reactivateHotel(id)
      return {
        content: [{ type: 'text', text: JSON.stringify(hotel, null, 2) }]
      }
    }
  • The tool schema definition including name, description, and inputSchema for 'reactivate_hotel' in the listTools method.
      name: 'reactivate_hotel',
      description: 'Reactivar un hotel',
      inputSchema: { type: 'object', properties: { id: { type: 'string', description: 'ID del hotel a reactivar' } }, required: ['id'] }
    },
  • src/index.ts:44-47 (registration)
    Registration of the tool call handler in the MCP server, which delegates to ToolsHandler.callTool for executing tools like 'reactivate_hotel'.
    this.server.setRequestHandler(
      CallToolRequestSchema,
      async (request) => await this.toolsHandler.callTool(request.params.name, request.params.arguments, this.server)
    )
  • The ApiService helper method that performs the actual API request to reactivate a hotel by ID.
    async reactivateHotel (id: string) {
      const headers = await this.getHeaders()
      const response = await fetch(`${API_CONFIG.baseUrl}/integrations/mcp/hotels/reactivate`, {
        method: 'PUT',
        headers,
        body: JSON.stringify({ id })
      })
      return await this.handleResponse<any>(response)
    }
  • src/index.ts:38-41 (registration)
    Registration of the listTools handler, which includes the 'reactivate_hotel' tool in the returned list.
    this.server.setRequestHandler(
      ListToolsRequestSchema,
      async () => this.toolsHandler.listTools()
    )
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. 'Reactivar' implies a mutation that changes a hotel's state, but it fails to specify required permissions, whether the operation is reversible, potential side effects (e.g., reactivating bookings), or error conditions. This is inadequate for a mutation tool with zero annotation coverage.

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 phrase ('Reactivar un hotel') with zero wasted words. It is appropriately sized and front-loaded, making it easy to parse quickly without unnecessary elaboration.

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 mutation tool with no annotations and no output schema, the description is incomplete. It lacks details on behavioral traits (e.g., what reactivation entails, success/failure responses), usage context, and differentiation from siblings. Given the complexity of state-changing operations, this minimal description does not provide sufficient guidance for an agent.

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 input schema has 100% description coverage, with the 'id' parameter documented as 'ID del hotel a reactivar'. The description adds no additional parameter information beyond what the schema provides, but since schema coverage is high, the baseline score of 3 is appropriate as the schema adequately handles parameter semantics.

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 'Reactivar un hotel' (Reactivate a hotel) is a tautology that restates the tool name 'reactivate_hotel' without adding meaningful context. It specifies the verb (reactivate) and resource (hotel) but lacks differentiation from sibling tools like 'reactivate_agency' or 'reactivate_program', failing to clarify what makes hotel reactivation unique.

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 on when to use this tool versus alternatives. The description does not mention prerequisites (e.g., the hotel must be deactivated), exclusions, or comparisons to sibling tools like 'create_hotel' or 'update_hotel', leaving the agent without context for appropriate selection.

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