Skip to main content
Glama
lumile

LumbreTravel MCP Server

by lumile

reactivate_service_language

Reactivate a previously disabled service language in the LumbreTravel system to restore its availability for travel programs and activities.

Instructions

Reactivar un idioma de servicio.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesID del idioma de servicio a reactivar

Implementation Reference

  • MCP tool handler implementation in callTool switch case. Extracts 'id' from args, calls apiService.reactivateServiceLanguage(id), and returns JSON response.
    case 'reactivate_service_language': {
      const { id } = args
      const serviceLanguage = await this.apiService.reactivateServiceLanguage(id)
      return {
        content: [{ type: 'text', text: JSON.stringify(serviceLanguage, null, 2) }]
      }
    }
  • Tool schema definition including name, description, and input schema requiring 'id' string.
    {
      name: 'reactivate_service_language',
      description: 'Reactivar un idioma de servicio.',
      inputSchema: { type: 'object', properties: { id: { type: 'string', description: 'ID del idioma de servicio a reactivar' } }, required: ['id'] }
    },
  • Tool registration within the listTools() method that returns all available MCP tools.
      }
    }
  • Core API service method that performs the PUT request to reactivate a service language by ID.
    async reactivateServiceLanguage (id: string) {
      const headers = await this.getHeaders()
      const response = await fetch(`${API_CONFIG.baseUrl}/integrations/mcp/servicelanguage/reactivate`, {
        method: 'PUT',
        headers,
        body: JSON.stringify({ id })
      })
      return await this.handleResponse<any>(response)
  • src/index.ts:44-47 (registration)
    MCP server registration of the callTool handler from ToolsHandler for executing tools.
    this.server.setRequestHandler(
      CallToolRequestSchema,
      async (request) => await this.toolsHandler.callTool(request.params.name, request.params.arguments, this.server)
    )
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. 'Reactivar' implies a mutation that changes state from inactive to active, but the description doesn't disclose behavioral traits like required permissions, whether it's idempotent, what happens on success/failure, or if it affects related entities. This is a significant gap for a mutation tool with zero 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 with zero waste. It's appropriately sized and front-loaded, directly stating the tool's purpose without unnecessary elaboration.

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 with no annotations and no output schema, the description is incomplete. It lacks context on behavior, error conditions, or what the tool returns. Given the complexity of state change operations and the absence of structured data, more information is needed for the agent to use this tool effectively.

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 input schema has 100% coverage with one parameter (id) fully described in Spanish. The description adds no parameter information beyond what the schema provides, so it meets the baseline of 3 where the schema does the heavy lifting.

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 'Reactivar un idioma de servicio' clearly states the action (reactivate) and resource (service language) in Spanish, which matches the tool name. It's specific but doesn't distinguish from sibling tools like reactivate_service or reactivate_agency, which follow the same pattern for different resources.

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. While the name implies it's for reactivating service languages, there's no mention of prerequisites (e.g., the language must be deactivated first) or when to choose this over creating a new service language with create_service_language.

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