Skip to main content
Glama
lumile

LumbreTravel MCP Server

by lumile

update_passengers

Edit passenger details including personal information, documents, and contact data for travel management within the LumbreTravel system.

Instructions

Edita pasajeros teniendo en cuenta que se conoce el ID del pasajero.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
passengersYes

Implementation Reference

  • MCP tool handler that calls apiService.updatePassengers with the input passengers array and formats the response as MCP content.
    case 'update_passengers': {
      const { passengers } = args as { passengers: any[] }
      const updatedPassengers = await this.apiService.updatePassengers(passengers)
      return {
        content: [{
          type: 'text',
          text: JSON.stringify(updatedPassengers, null, 2)
        }]
      }
    }
  • Input schema defining the structure for updating passengers, requiring an array of passenger objects each with passengerId and other personal details.
    inputSchema: {
      type: 'object',
      properties: {
        passengers: {
          type: 'array',
          items: {
            type: 'object',
            properties: {
              passengerId: { type: 'string' },
              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' },
              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: ['passengerId', 'firstname', 'lastname', 'birthdate', 'documenttype', 'document', 'gender', 'nationality', 'language', 'email', 'phone']
          }
        }
      },
      required: ['passengers']
    }
  • Tool registration in the listTools() array, specifying name, description, and inputSchema.
    {
      name: 'update_passengers',
      description: 'Edita pasajeros teniendo en cuenta que se conoce el ID del pasajero.',
      inputSchema: {
        type: 'object',
        properties: {
          passengers: {
            type: 'array',
            items: {
              type: 'object',
              properties: {
                passengerId: { type: 'string' },
                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' },
                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: ['passengerId', 'firstname', 'lastname', 'birthdate', 'documenttype', 'document', 'gender', 'nationality', 'language', 'email', 'phone']
            }
          }
        },
        required: ['passengers']
      }
    },
  • ApiService helper method that sends a POST request to the backend endpoint /integrations/mcp/passengers/update_passengers with the passengers data.
    async updatePassengers (passengers: any[]) {
      const headers = await this.getHeaders()
      const response = await fetch(`${API_CONFIG.baseUrl}/integrations/mcp/passengers/update_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?

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the tool edits passengers, implying a mutation operation, but doesn't disclose critical behavioral traits: whether it requires specific permissions, if changes are reversible, what happens to unspecified fields (partial vs full updates), error handling, or rate limits. The description adds minimal context beyond the basic edit action.

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's reasonably concise, but it's not optimally structured. It front-loads the main action ('Edita pasajeros') but buries the important constraint about passenger ID in a subordinate clause. While not wasteful, it could be more direct and better organized to highlight key information first.

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 complexity (11 required nested parameters, mutation operation), absence of annotations, and no output schema, the description is incomplete. It doesn't explain what constitutes a successful edit, return values, error conditions, or the scope of changes. For a tool with such rich parameter requirements and no structured documentation support, the description provides inadequate context for proper tool invocation.

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

Parameters1/5

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

The description provides zero information about parameters beyond implying passenger ID is involved. With schema description coverage at 0% (no parameter descriptions in schema) and 11 required nested parameters, the description fails to compensate. It doesn't explain what 'passengers' array contains, the meaning of fields like 'documenttype' or 'gender', or default behaviors mentioned in schema descriptions (e.g., deducing values from names).

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 states the tool 'edits passengers' which is a clear verb+resource combination, but it's vague about what specific aspects are edited. It mentions 'teniendo en cuenta que se conoce el ID del pasajero' (considering that the passenger ID is known), which adds some context but doesn't fully distinguish it from sibling tools like 'update_activities' or 'update_program' 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 Guidelines2/5

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

The description provides no explicit guidance on when to use this tool versus alternatives. While it implies usage when passenger ID is known, it doesn't mention when NOT to use it (e.g., vs 'create_passengers' for new passengers or 'delete_passenger' for removal) or reference any sibling tools. The phrase about knowing the ID is more of a prerequisite than usage guidance.

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