Skip to main content
Glama
lumile

LumbreTravel MCP Server

by lumile

get_passengers_by_fullname

Retrieve passenger information from the LumbreTravel MCP Server by searching with a full name. This tool helps find specific passengers in travel management systems.

Instructions

Obtiene pasajeros por nombre completo

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fullnameYesNombre completo del pasajero

Implementation Reference

  • Handler logic in callTool method that extracts fullname argument, calls ApiService.getPassengersByFullname, and returns JSON stringified response.
    case 'get_passengers_by_fullname': {
      const { fullname } = args as { fullname: string }
      const passengers = await this.apiService.getPassengersByFullname(fullname)
      return {
        content: [{
          type: 'text',
          text: JSON.stringify(passengers, null, 2)
        }]
      }
    }
  • Tool schema definition in listTools method, including name, description, and input schema requiring 'fullname' string.
      name: 'get_passengers_by_fullname',
      description: 'Obtiene pasajeros por nombre completo',
      inputSchema: {
        type: 'object',
        properties: {
          fullname: { type: 'string', description: 'Nombre completo del pasajero' }
        },
        required: ['fullname']
      }
    },
  • Helper method in ApiService that performs authenticated POST request to backend API endpoint for fetching passengers by fullname.
    async getPassengersByFullname (fullname: string) {
      const headers = await this.getHeaders()
      const response = await fetch(`${API_CONFIG.baseUrl}/integrations/mcp/passengers/get_passengers_by_fullname`, {
        method: 'POST',
        headers: { ...headers, 'Content-Type': 'application/json' },
        body: JSON.stringify({ fullname })
      })
      return await this.handleResponse<any>(response)
    }
Behavior1/5

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

No annotations are provided, so the description carries full burden. It only states the action without disclosing behavioral traits like read-only vs. destructive, authentication needs, rate limits, error handling, or return format. This is inadequate for a tool with no annotation coverage.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence in Spanish, front-loaded with the core action. There's zero waste, making it appropriately concise and well-structured for its purpose.

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 no annotations, no output schema, and a simple parameter, the description is incomplete. It lacks details on behavior, usage context, and output, making it insufficient for an agent to reliably invoke the tool without guesswork.

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%, with the parameter 'fullname' documented as 'Nombre completo del pasajero'. The description adds no additional meaning beyond the schema, such as format examples or search behavior. Baseline 3 is appropriate since the schema does the heavy lifting.

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 nombre completo' (Gets passengers by full name) states the verb and resource, but it's vague about scope (e.g., exact match, partial, case-sensitive) and doesn't differentiate from sibling 'get_passengers_by_email'. It's not tautological but lacks specificity for a 4 or 5.

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 'get_passengers_by_email' or 'list_passengers' (if existed). The description implies usage by full name but doesn't specify scenarios, exclusions, or prerequisites, leaving the agent to guess.

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