Skip to main content
Glama
lumile

LumbreTravel MCP Server

by lumile

delete_passenger

Remove a passenger from travel records by specifying their unique ID to maintain accurate booking information.

Instructions

Elimina un pasajero teniendo en cuenta que se conoce su ID

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
passengerIdYes

Implementation Reference

  • Handler implementation for the 'delete_passenger' tool in the callTool method. Extracts passengerId from args, calls apiService.deletePassenger, and returns the JSON stringified result.
    case 'delete_passenger': {
      const { passengerId } = args as { passengerId: string }
      const deletedPassenger = await this.apiService.deletePassenger(passengerId)
      return {
        content: [{ type: 'text', text: JSON.stringify(deletedPassenger, null, 2) }]
      }
    }
  • Schema definition and registration for the 'delete_passenger' tool within the listTools method, including name, description, and input schema requiring 'passengerId'.
    {
      name: 'delete_passenger',
      description: 'Elimina un pasajero teniendo en cuenta que se conoce su ID',
      inputSchema: {
        type: 'object',
        properties: {
          passengerId: { type: 'string' }
        },
        required: ['passengerId']
      }
    },
  • Helper method in ApiService that performs the actual API call to delete a passenger by ID via DELETE request to /passengers/delete/{passengerId}, used by the tool handler.
    async deletePassenger (passengerId: string) {
      const headers = await this.getHeaders()
      const response = await fetch(`${API_CONFIG.baseUrl}/integrations/mcp/passengers/delete/${passengerId}`, {
        method: 'DELETE',
        headers
      })
      return await this.handleResponse<any>(response)
    }
  • src/index.ts:44-47 (registration)
    Server registration for handling tool calls via CallToolRequestSchema, which routes to toolsHandler.callTool based on the tool name, enabling execution of 'delete_passenger'.
    this.server.setRequestHandler(
      CallToolRequestSchema,
      async (request) => await this.toolsHandler.callTool(request.params.name, request.params.arguments, this.server)
    )
  • src/index.ts:38-41 (registration)
    Server registration for listing available tools via ListToolsRequestSchema, which includes the 'delete_passenger' tool from toolsHandler.listTools.
    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 full burden for behavioral disclosure. While 'Elimina' clearly indicates a destructive operation, the description doesn't specify whether this is a hard or soft deletion, whether it's reversible, what permissions are required, what happens to associated data, or what the response looks like. For a destructive operation with zero annotation coverage, this represents significant gaps in behavioral transparency.

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 Spanish sentence that gets straight to the point. There's no wasted language or unnecessary elaboration. However, it could be more front-loaded with critical behavioral information given this is a destructive operation.

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 deletion tool with no annotations, no output schema, and 0% schema description coverage, the description is incomplete. It doesn't address critical questions about deletion behavior (hard vs soft, reversibility), error conditions, permissions, or what happens to related data. The presence of 'reactivate_passenger' as a sibling tool suggests a soft deletion system exists, making this omission particularly significant.

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 description must compensate. The description mentions 'se conoce su ID' (its ID is known), which provides some context about the passengerId parameter, but doesn't explain the ID format, where to find it, or provide any examples. With 1 parameter completely undocumented in the schema, the description adds minimal semantic value beyond what's obvious from the parameter name.

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' - delete/destroy) and the resource ('un pasajero' - a passenger), which is specific and unambiguous. However, it doesn't differentiate from sibling tools like 'delete_passengers' (plural) or 'reactivate_passenger', leaving some ambiguity about when to use this singular deletion tool versus the batch deletion tool.

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 minimal guidance - it only mentions that the passenger ID must be known. It doesn't explain when to use this tool versus alternatives like 'delete_passengers' (plural deletion), 'reactivate_passenger' (which suggests soft deletion might be available), or when deletion is appropriate versus updating passenger data. No explicit when/when-not guidance is provided.

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