Skip to main content
Glama
lumile

LumbreTravel MCP Server

by lumile

create_passengers

Add passenger details to travel bookings by processing names, birthdates, documents, and contact information for trip arrangements.

Instructions

Crea pasajeros, usa esta tool cuando el asistente recibe los datos de los pasajeros como parte del pedido del usuario

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
passengersYes

Implementation Reference

  • MCP tool handler for 'create_passengers': extracts arguments, calls ApiService.createPassengers, formats and returns the response as text content.
    case 'create_passengers': {
      const { passengers, programId } = args as { passengers: any[], programId: string }
      const createdPassengers = await this.apiService.createPassengers(passengers, programId)
      return {
        content: [{
          type: 'text',
          text: JSON.stringify(createdPassengers, null, 2)
        }]
      }
    }
  • Input schema definition and registration of the 'create_passengers' tool in the listTools() method, including name, description, and detailed inputSchema for passengers array.
    {
      name: 'create_passengers',
      description: 'Crea pasajeros, usa esta tool cuando el asistente recibe los datos de los pasajeros como parte del pedido del usuario',
      inputSchema: {
        type: 'object',
        properties: {
          passengers: {
            type: 'array',
            items: {
              type: 'object',
              properties: {
                firstname: { type: 'string' },
                lastname: { type: 'string' },
                birthdate: { type: 'string', description: "Fecha de nacimiento del pasajero (DD-MM-YYYY), si no se especifica usa el valor 'No conocemos'" },
                documenttype: { type: 'string', description: 'Tipo de documento, opciones válidas son DNI, Pasaporte, Licencia de Conducir o ID.  Si no se especifica el valor por defecto es ID.' },
                document: { type: 'string', description: "Numero de documento, si no se especifica usa el valor 'No conocemos'" },
                gender: { type: 'string', description: 'Género del pasajero, puede ser male, female,non_binary, prefer_not_to_say, other.  Si no se especifica deducilo del nombre y apellido' },
                nationality: {
                  type: 'string',
                  description: 'Nacionalidad del pasajero de acuerdo a ISO 3166-1.  Si no se especifica deducilo del nombre y apellido'
                },
                language: {
                  type: 'string',
                  description: "Idioma del pasajero de acuerdo a ISO 639-1.  Si no se especifica deducilo del nombre y apellido.  No intentes usar las tools 'list_service_languages' ni 'get_service_language_by_name' para obtener el idioma del pasajero.  El idioma del pasajero es simplemente un string en formato ISO 639-1."
                },
                email: { type: 'string', description: "Email del pasajero, si no se especifica usa el valor 'No conocemos'" },
                phone: { type: 'string', description: "Telefono del pasajero, si no se especifica usa el valor 'No conocemos'" }
              },
              required: ['firstname', 'lastname', 'birthdate', 'documenttype', 'document', 'gender', 'nationality', 'language', 'email', 'phone']
            }
          }
        },
        required: ['passengers']
      }
    },
  • Helper method in ApiService that performs the actual HTTP POST request to the backend API endpoint /integrations/mcp/passengers/create_passengers to create passengers for a program.
    async createPassengers (passengers: any[], programId: string) {
      const headers = await this.getHeaders()
      const response = await fetch(`${API_CONFIG.baseUrl}/integrations/mcp/passengers/create_passengers`, {
        method: 'POST',
        headers: { ...headers, 'Content-Type': 'application/json' },
        body: JSON.stringify({ passengers, programId })
      })
      return await this.handleResponse<any>(response)
    }
  • src/index.ts:44-47 (registration)
    MCP server registration of the generic callTool handler, which dispatches to ToolsHandler.callTool based on tool name, enabling execution of 'create_passengers'.
    this.server.setRequestHandler(
      CallToolRequestSchema,
      async (request) => await this.toolsHandler.callTool(request.params.name, request.params.arguments, this.server)
    )
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. It states the tool creates passengers but doesn't mention whether this is a write operation, what permissions are required, whether it's idempotent, what happens on failure, or what the return value looks like. For a creation tool with zero annotation coverage, this leaves significant behavioral gaps that could affect agent decision-making.

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 appropriately concise with just one sentence in Spanish. It front-loads the core purpose ('Crea pasajeros') followed by usage context. There's no wasted text, though it could benefit from slightly more detail given the complexity of passenger creation.

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 creation tool with no annotations, no output schema, and 1 parameter (though complex with nested objects), the description is insufficient. It doesn't address behavioral aspects like error handling, authentication requirements, or response format. While the input schema provides detailed property descriptions, the description itself doesn't add meaningful context about the creation operation's semantics or constraints.

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?

The description provides no information about the single parameter 'passengers' beyond what's implied by the tool name. With 0% schema description coverage (the schema has descriptions but they're not counted in coverage metrics), the description fails to compensate for the lack of parameter documentation. It doesn't explain what the passengers array should contain, format expectations, or any constraints beyond the basic creation context.

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 tool's purpose: 'Crea pasajeros' (creates passengers) which is a specific verb+resource combination. It distinguishes itself from sibling tools like 'add_passengers_to_program' or 'update_passengers' by focusing on initial creation rather than modification or addition to existing entities. However, it doesn't explicitly differentiate from 'create_agency' or other 'create_' tools beyond the resource type.

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

Usage Guidelines3/5

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

The description provides some usage guidance: 'usa esta tool cuando el asistente recibe los datos de los pasajeros como parte del pedido del usuario' (use this tool when the assistant receives passenger data as part of the user's order). This implies the context but doesn't explicitly state when NOT to use it or mention alternatives like 'add_passengers_to_program' for adding to existing programs. The guidance is helpful but incomplete.

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