Skip to main content
Glama
lumile

LumbreTravel MCP Server

by lumile

reactivate_program

Reactivate a travel program by providing its ID to restore access and functionality within the LumbreTravel system.

Instructions

Reactiva un programa de viajes

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes

Implementation Reference

  • Tool handler implementation for 'reactivate_program'. Extracts the program ID from input arguments, calls ApiService.reactivateProgram(id), and returns the result as a JSON-formatted text content block.
    case 'reactivate_program': {
      const { id } = args as { id: string }
      const program = await this.apiService.reactivateProgram(id)
      return {
        content: [{ type: 'text', text: JSON.stringify(program, null, 2) }]
      }
    }
  • Tool registration entry in listTools() method, including name, description, and input schema requiring a string 'id'.
    {
      name: 'reactivate_program',
      description: 'Reactiva un programa de viajes',
      inputSchema: {
        type: 'object',
        properties: {
          id: { type: 'string' }
        },
        required: ['id']
      }
    },
  • Input schema for 'reactivate_program' tool: object with required 'id' property of type string.
    inputSchema: {
      type: 'object',
      properties: {
        id: { type: 'string' }
      },
      required: ['id']
    }
  • Supporting helper method in ApiService that performs the actual API call to reactivate a program by ID via PUT request to the backend endpoint.
    async reactivateProgram (id: string) {
      const headers = await this.getHeaders()
      const response = await fetch(`${API_CONFIG.baseUrl}/integrations/mcp/programs/reactivate/${id}`, {
        method: 'PUT',
        headers
      })
      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 full burden. 'Reactiva' implies a state change (likely from inactive to active), but it doesn't disclose behavioral traits like required permissions, whether this is reversible, what happens to associated data, or error conditions. For a mutation tool with zero annotation coverage, this is a significant gap.

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 with zero waste. It's appropriately sized and front-loaded, though its brevity contributes to gaps in other dimensions.

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 tool's complexity (a mutation operation), lack of annotations, no output schema, and 0% schema description coverage, the description is incomplete. It fails to address key aspects like parameter meaning, usage context, behavioral implications, or expected outcomes, making it inadequate for safe and effective use.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must compensate. It mentions no parameters at all—not even hinting at the required 'id' parameter for identifying which program to reactivate. This leaves the single parameter completely undocumented beyond the schema's type information.

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 'Reactiva un programa de viajes' clearly states the action (reactivate) and resource (travel program) in Spanish. It's specific about what the tool does, though it doesn't explicitly differentiate from sibling tools like 'reactivate_agency' or 'reactivate_hotel' 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 guidance on when to use this tool versus alternatives. With siblings like 'update_program' and 'create_program' available, there's no indication of prerequisites (e.g., program must be deactivated first) or when reactivation is appropriate versus creating a new program.

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