Skip to main content
Glama
lumile

LumbreTravel MCP Server

by lumile

delete_hotel

Remove a hotel from the LumbreTravel travel program by specifying its unique ID to manage accommodation listings.

Instructions

Eliminar un hotel

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesID del hotel a eliminar

Implementation Reference

  • MCP tool handler case for 'delete_hotel': extracts id from args, calls apiService.deleteHotel(id), and formats response as text content with JSON stringified hotel data.
    case 'delete_hotel': {
      const { id } = args as { id: string }
      const hotel = await this.apiService.deleteHotel(id)
      return {
        content: [{ type: 'text', text: JSON.stringify(hotel, null, 2) }]
      }
    }
  • Tool definition in listTools(): registers 'delete_hotel' with description and input schema requiring 'id' as string.
      name: 'delete_hotel',
      description: 'Eliminar un hotel',
      inputSchema: {
        type: 'object',
        properties: { id: { type: 'string', description: 'ID del hotel a eliminar' } },
        required: ['id']
      }
    },
  • Core implementation of deleteHotel: sends DELETE request to /integrations/mcp/hotels/delete/{id} with auth headers and handles response.
    async deleteHotel (id: string) {
      const headers = await this.getHeaders()
      const response = await fetch(`${API_CONFIG.baseUrl}/integrations/mcp/hotels/delete/${id}`, {
        method: 'DELETE',
        headers
      })
      return await this.handleResponse<any>(response)
    }
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. 'Eliminar' implies a destructive operation, but it doesn't specify if deletion is permanent, requires specific permissions, has side effects (e.g., on related data), or what happens on success/failure. This leaves critical behavioral traits unclear for a mutation tool.

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 a single, efficient phrase ('Eliminar un hotel') that directly states the action. It's appropriately sized and front-loaded with no wasted words, though it could be slightly more informative without losing conciseness.

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 destructive tool with no annotations and no output schema, the description is incomplete. It doesn't cover behavioral aspects like permanence, error handling, or return values, which are crucial for safe and effective use by an AI 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 clearly documented as 'ID del hotel a eliminar'. The description adds no additional parameter semantics beyond what the schema provides, so it meets the baseline for high schema coverage.

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 'Eliminar un hotel' (Delete a hotel) clearly states the verb and resource, making the purpose understandable. However, it doesn't differentiate from sibling deletion tools like delete_agency or delete_program, which follow the same pattern, so it lacks specific distinction.

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?

No guidance is provided on when to use this tool versus alternatives. For example, it doesn't mention prerequisites like checking if a hotel exists first or when to use reactivate_hotel instead. The description offers no context for selection among sibling tools.

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