Skip to main content
Glama
lumile

LumbreTravel MCP Server

by lumile

add_passengers_to_program

Add passengers to a travel program by providing program ID and passenger details to manage participant lists for organized trips.

Instructions

Agrega pasajeros a un programa.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
programIdYesID del programa
passengersYesLista de pasajeros

Implementation Reference

  • Core handler function that makes the API call to add passengers to a program.
    async addPassengersToProgram (programId: string, passengers: any[]) {
      const headers = await this.getHeaders()
      const response = await fetch(`${API_CONFIG.baseUrl}/integrations/mcp/programs/add_passengers`, {
        method: 'POST',
        headers: { ...headers, 'Content-Type': 'application/json' },
        body: JSON.stringify({ programId, passengers })
      })
      return await this.handleResponse<any>(response)
    }
  • MCP tool handler wrapper that calls the ApiService method and formats the response.
    case 'add_passengers_to_program': {
      const { programId, passengers } = args as { programId: string, passengers: any[] }
      const addedPassengers = await this.apiService.addPassengersToProgram(programId, passengers)
      return {
        content: [{ type: 'text', text: JSON.stringify(addedPassengers, null, 2) }]
      }
    }
  • Tool registration including name, description, and input schema in listTools() method.
      name: 'add_passengers_to_program',
      description: 'Agrega pasajeros a un programa.',
      inputSchema: {
        type: 'object',
        properties: {
          programId: { type: 'string', description: 'ID del programa' },
          passengers: {
            type: 'array',
            description: 'Lista de pasajeros',
            items: {
              type: 'object',
              properties: {
                id: { type: 'string' },
                name: { type: 'string' }
              },
              required: ['id', 'name']
            }
          }
        },
        required: ['programId', 'passengers']
      }
    },
  • Input schema definition for the tool parameters.
      type: 'object',
      properties: {
        programId: { type: 'string', description: 'ID del programa' },
        passengers: {
          type: 'array',
          description: 'Lista de pasajeros',
          items: {
            type: 'object',
            properties: {
              id: { type: 'string' },
              name: { type: 'string' }
            },
            required: ['id', 'name']
          }
        }
      },
      required: ['programId', 'passengers']
    }
Behavior2/5

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

With no annotations provided, the description carries full burden but only states the action ('adds') without disclosing behavioral traits. It doesn't mention whether this is a mutation, what permissions are needed, if duplicates are allowed, how failures are handled, or what the response looks like. For a write operation with zero annotation coverage, this is inadequate.

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 sentence in Spanish that directly states the tool's purpose. It's appropriately brief and front-loaded with the core action, though it could benefit from slightly more detail given the lack of annotations and output schema.

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 mutation tool with no annotations, no output schema, and multiple similar sibling tools, the description is incomplete. It doesn't address behavioral aspects, usage context, or result expectations. The agent would need to guess about important operational details when invoking this tool.

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?

Schema description coverage is 100%, so the schema already documents both parameters (programId and passengers). The description doesn't add any meaning beyond what the schema provides - no explanation of what constitutes valid program IDs, passenger data formats, or constraints. Baseline 3 is appropriate when schema does the documentation work.

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 'Agrega pasajeros a un programa' clearly states the action (adds) and target (passengers to a program), but it's vague about scope and doesn't distinguish from sibling tools like 'create_passengers' or 'update_passengers'. It provides basic purpose but lacks specificity about what 'adding' entails in this context.

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 on when to use this tool versus alternatives like 'create_passengers' or 'update_passengers'. The description doesn't mention prerequisites, constraints, or appropriate contexts for use, leaving the agent with no usage differentiation from similar-sounding 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