Skip to main content
Glama
lumile

LumbreTravel MCP Server

by lumile

reactivate_passenger

Reactivate a passenger account using their ID to restore access to travel programs and activities in the LumbreTravel system.

Instructions

Reactiva un pasajero teniendo en cuenta que se conoce su ID

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes

Implementation Reference

  • Registration of the 'reactivate_passenger' tool including its name, description, and input schema in the listTools method.
    {
      name: 'reactivate_passenger',
      description: 'Reactiva un pasajero teniendo en cuenta que se conoce su ID',
      inputSchema: {
        type: 'object',
        properties: {
          id: { type: 'string' }
        },
        required: ['id']
      }
    },
  • Handler execution for 'reactivate_passenger' tool: extracts id from args, calls apiService.reactivatePassenger, and returns JSON response.
    case 'reactivate_passenger': {
      const { id } = args as { id: string }
      const reactivatedPassenger = await this.apiService.reactivatePassenger(id)
      return {
        content: [{ type: 'text', text: JSON.stringify(reactivatedPassenger, null, 2) }]
      }
    }
  • Helper function in ApiService that sends PUT request to backend API to reactivate the passenger by ID.
    async reactivatePassenger (id: string) {
      const headers = await this.getHeaders()
      const response = await fetch(`${API_CONFIG.baseUrl}/integrations/mcp/passengers/reactivate`, {
        method: 'PUT',
        headers,
        body: JSON.stringify({ id })
      })
      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 of behavioral disclosure. 'Reactiva' implies a mutation that changes state (likely from inactive to active), but the description doesn't clarify permissions required, side effects (e.g., impact on related data), or what 'reactivation' entails (e.g., restoring access, resetting status). It lacks details on error conditions or response format, leaving behavioral traits unclear.

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 that directly states the tool's purpose and key constraint. It's front-loaded with the main action and resource, with no redundant information, making it appropriately sized and easy to parse.

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 (a mutation tool with no annotations and no output schema), the description is incomplete. It lacks details on what 'reactivation' means operationally, expected outcomes, error handling, or how it differs from other passenger-related tools (e.g., delete_passenger, update_passengers). For a tool that likely changes system state, more context is needed to ensure correct usage.

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

Parameters4/5

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

The input schema has 1 parameter (id) with 0% description coverage, so the schema provides no semantic information. The description adds meaning by specifying that the ID must be known ('se conoce su ID'), which clarifies the parameter's role as a pre-existing identifier. However, it doesn't detail the ID format (e.g., numeric, string pattern) or source, leaving some ambiguity.

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 action ('reactiva') and target resource ('un pasajero'), making the purpose understandable. It specifies that the passenger ID must be known, which adds useful context. However, it doesn't explicitly differentiate from sibling reactivate_* tools (like reactivate_agency, reactivate_hotel, etc.), which all follow the same pattern.

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 minimal guidance by stating 'se conoce su ID' (its ID is known), implying the prerequisite of having the passenger ID. However, it offers no explicit guidance on when to use this tool versus alternatives (like update_passengers or create_passengers), nor does it mention any exclusions or specific scenarios for reactivation.

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