Skip to main content
Glama
lumile

LumbreTravel MCP Server

by lumile

reactivate_include

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

Instructions

Reactivar un extra o incluído

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesID del include a reactivar

Implementation Reference

  • The handler logic in callTool that processes the 'reactivate_include' tool invocation by calling the ApiService method.
    case 'reactivate_include': {
      const { id } = args as { id: string }
      const include = await this.apiService.reactivateInclude(id)
      return {
        content: [{ type: 'text', text: JSON.stringify(include, null, 2) }]
      }
    }
  • Tool schema definition including name, description, and input schema for validation in listTools().
    {
      name: 'reactivate_include',
      description: 'Reactivar un extra o incluído',
      inputSchema: { type: 'object', properties: { id: { type: 'string', description: 'ID del include a reactivar' } }, required: ['id'] }
    },
  • Supporting service method in ApiService that performs the actual API call to reactivate an include.
    async reactivateInclude (id: string) {
      const headers = await this.getHeaders()
      const response = await fetch(`${API_CONFIG.baseUrl}/integrations/mcp/include/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?

With no annotations provided, the description carries full burden but offers minimal behavioral insight. It implies a state change (reactivation) but doesn't disclose effects (e.g., whether it restores associated data, requires permissions, or has side effects). For a mutation tool with zero annotation coverage, this is a significant gap in transparency.

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 ('Reactivar un extra o incluído') with zero wasted words. It's appropriately sized and front-loaded, making it easy to parse quickly.

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 (reactivation) with no annotations and no output schema, the description is incomplete. It lacks details on behavior, side effects, error conditions, or return values, which are crucial for safe and effective use by an AI agent in this context.

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 with 100% description coverage ('ID del include a reactivar'), so the schema fully documents the parameter. The description adds no extra parameter details, but with high schema coverage and only one parameter, a baseline of 4 is appropriate as the description doesn't need to compensate.

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 'Reactivar un extra o incluído' clearly states the action (reactivate) and target (an extra or include), which is better than a tautology. However, it's vague about what 'reactivate' entails operationally and doesn't distinguish this tool from sibling reactivation tools like reactivate_agency or reactivate_hotel, missing specific differentiation.

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. The description doesn't mention prerequisites (e.g., that the include must be deactivated first), exclusions, or refer to sibling tools like delete_include or create_include for context, leaving usage unclear.

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