Skip to main content
Glama
lumile

LumbreTravel MCP Server

by lumile

delete_passengers

Remove passengers from travel programs by specifying their unique IDs to manage participant lists and update booking information.

Instructions

Elimina pasajeros teniendo en cuenta que se conoce el ID del pasajero

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
passengersYes

Implementation Reference

  • The main handler logic for the 'delete_passengers' MCP tool. It extracts the list of passengers from the input arguments and delegates the deletion to the ApiService.deletePassengers method, returning the API response as tool output.
    case 'delete_passengers': {
      const { passengers } = args as { passengers: any[] }
      const deletedPassengers = await this.apiService.deletePassengers(passengers)
      return {
        content: [{ type: 'text', text: JSON.stringify(deletedPassengers, null, 2) }]
      }
    }
  • The tool definition including name, description, and input schema for validation of arguments (array of passenger objects with 'id'). This is returned by listTools().
    {
      name: 'delete_passengers',
      description: 'Elimina pasajeros teniendo en cuenta que se conoce el ID del pasajero',
      inputSchema: {
        type: 'object',
        properties: {
          passengers: {
            type: 'array',
            items: {
              type: 'object',
              properties: {
                id: {
                  type: 'string',
                  description: 'ID del pasajero a eliminar'
                }
              },
              required: ['id']
            }
          }
        },
        required: ['passengers']
      }
  • src/index.ts:44-47 (registration)
    Registration of the callTool handler on the MCP server, which routes tool calls (including 'delete_passengers') to ToolsHandler.callTool.
    this.server.setRequestHandler(
      CallToolRequestSchema,
      async (request) => await this.toolsHandler.callTool(request.params.name, request.params.arguments, this.server)
    )
  • Supporting API service method that performs the actual HTTP POST request to the backend endpoint /integrations/mcp/passengers/delete_passengers to delete the specified passengers.
    async deletePassengers (passengers: any[]) {
      const headers = await this.getHeaders()
      const response = await fetch(`${API_CONFIG.baseUrl}/integrations/mcp/passengers/delete_passengers`, {
        method: 'POST',
        headers: { ...headers, 'Content-Type': 'application/json' },
        body: JSON.stringify({ passengers })
      })
      return await this.handleResponse<any>(response)
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It states it's a deletion operation ('Elimina'), implying it's destructive, but doesn't disclose critical behavioral traits such as whether deletions are permanent, reversible via reactivation tools, require specific permissions, or have side effects on related data. For a destructive tool with zero annotation coverage, this is a significant gap in transparency.

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 that is reasonably concise, but it's not optimally structured. It front-loads the action and resource but could be more direct. While it avoids unnecessary words, it lacks clarity in distinguishing from siblings, making it somewhat inefficient in conveying full utility.

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?

Given the tool's destructive nature, lack of annotations, no output schema, and low parameter semantics, the description is incomplete. It doesn't cover behavioral aspects like permanence, error handling, or relationships with reactivation tools, nor does it provide usage context. This leaves the agent poorly equipped to use the tool safely and effectively.

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

Parameters2/5

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

Schema description coverage is 0%, so the schema provides no parameter descriptions. The description adds minimal semantics by mentioning that passenger IDs are required ('se conoce el ID del pasajero'), but it doesn't explain the array structure, format of IDs, or any constraints. This is inadequate compensation for the lack of schema documentation, leaving parameters largely unexplained.

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 action ('Elimina' meaning 'Delete') and the resource ('pasajeros' meaning 'passengers'), specifying it requires passenger IDs. It distinguishes from siblings like 'delete_passenger' (singular) by indicating it handles multiple passengers. However, it doesn't fully clarify if it's batch deletion or how it differs from other deletion tools beyond the plural form.

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 no guidance on when to use this tool versus alternatives like 'delete_passenger' (singular) or 'reactivate_passenger'. It mentions the requirement of passenger IDs but gives no context about prerequisites, error conditions, or typical use cases. This leaves the agent with insufficient information to choose appropriately 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