Skip to main content
Glama
lumile

LumbreTravel MCP Server

by lumile

get_passengers_by_email

Retrieve passenger information from the LumbreTravel MCP Server by searching with an email address to manage travel program data.

Instructions

Obtiene pasajeros por email

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
emailYesEmail del pasajero

Implementation Reference

  • Registers the MCP tool 'get_passengers_by_email' including its name, description, and input schema in the listTools() response.
      name: 'get_passengers_by_email',
      description: 'Obtiene pasajeros por email',
      inputSchema: {
        type: 'object',
        properties: {
          email: { type: 'string', description: 'Email del pasajero' }
        },
        required: ['email']
      }
    },
  • Input schema definition for the 'get_passengers_by_email' tool, requiring an 'email' string parameter.
    inputSchema: {
      type: 'object',
      properties: {
        email: { type: 'string', description: 'Email del pasajero' }
      },
      required: ['email']
    }
  • MCP tool handler implementation in callTool method: extracts email from args, calls ApiService.getPassengersByEmail, and returns JSON-formatted passengers.
    case 'get_passengers_by_email': {
      const { email } = args as { email: string }
      const passengers = await this.apiService.getPassengersByEmail(email)
      return {
        content: [{
          type: 'text',
          text: JSON.stringify(passengers, null, 2)
        }]
      }
    }
  • Helper service method that performs authenticated POST request to backend API endpoint /integrations/mcp/passengers/get_passengers_by_email with the email.
    async getPassengersByEmail (email: string) {
      const headers = await this.getHeaders()
      const response = await fetch(`${API_CONFIG.baseUrl}/integrations/mcp/passengers/get_passengers_by_email`, {
        method: 'POST',
        headers: { ...headers, 'Content-Type': 'application/json' },
        body: JSON.stringify({ email })
      })
      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 a read operation ('obtiene'), implying non-destructive behavior, but doesn't disclose critical traits like authentication needs, rate limits, error handling, or return format (e.g., list of passengers, single record). For a tool with zero annotation coverage, this is a significant gap in behavioral context.

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 ('Obtiene pasajeros por email'), which is appropriately sized and front-loaded with the core action. However, it could be more structured by including key details like scope or alternatives, but it avoids unnecessary verbosity.

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 of a lookup tool with no annotations and no output schema, the description is incomplete. It doesn't explain what 'pasajeros' includes (e.g., fields returned), how results are formatted, or error cases. For a tool that likely returns passenger data, more context is needed to guide effective use.

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?

The schema description coverage is 100%, with the parameter 'email' documented as 'Email del pasajero'. The description adds no additional meaning beyond this, such as format requirements or examples. With high schema coverage, the baseline is 3, as the schema adequately handles parameter documentation without extra input from the description.

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 'Obtiene pasajeros por email' (Gets passengers by email) states a clear verb ('obtiene') and resource ('pasajeros'), but it's vague about scope and doesn't distinguish from sibling tools like 'get_passengers_by_fullname' or 'list' operations. It specifies the lookup method ('por email') but lacks detail on what 'pasajeros' entails (e.g., passenger records, details).

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 is provided on when to use this tool versus alternatives. With siblings like 'get_passengers_by_fullname' and 'list' tools, the description doesn't indicate whether this is for exact email matches, partial searches, or when email is the preferred identifier over names. Usage context is implied but not explicit.

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