Skip to main content
Glama
lumile

LumbreTravel MCP Server

by lumile

list_service_languages

Retrieve available languages for associating with travel activity services in travel programs.

Instructions

Obtiene todos los idiomas para asociar a una actividad en un programa de viajes. Estos idiomas solo se pueden usar para asociar a un servicio.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler implementation for the 'list_service_languages' tool. It calls apiService.getServiceLanguages() and returns the JSON stringified result as text content.
    case 'list_service_languages': {
      const serviceLanguages = await this.apiService.getServiceLanguages()
      return {
        content: [{
          type: 'text',
          text: JSON.stringify(serviceLanguages, null, 2)
        }]
      }
    }
  • Input schema definition for the 'list_service_languages' tool in the listTools() method. No input parameters required.
    {
      name: 'list_service_languages',
      description: 'Obtiene todos los idiomas para asociar a una actividad en un programa de viajes.  Estos idiomas solo se pueden usar para asociar a un servicio.',
      inputSchema: {
        type: 'object',
        properties: {}
      }
    },
  • ApiService method that performs the actual GET request to retrieve service languages from the LumbreTravel API.
    async getServiceLanguages () {
      const headers = await this.getHeaders()
      const response = await fetch(`${API_CONFIG.baseUrl}/integrations/mcp/servicelanguages`, {
        method: 'GET',
        headers
      })
      return await this.handleResponse<any[]>(response)
    }
  • src/index.ts:38-47 (registration)
    MCP server request handlers registration for tool listing (ListToolsRequestSchema) and tool calling (CallToolRequestSchema), which invoke the ToolsHandler methods containing the tool implementation.
    this.server.setRequestHandler(
      ListToolsRequestSchema,
      async () => this.toolsHandler.listTools()
    )
    
    // Configure handlers for 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 the full burden. It describes the action (retrieves all languages) and a constraint on usage (only for associating with services), but lacks behavioral details such as whether this is a read-only operation, potential rate limits, authentication requirements, response format, or pagination behavior. For a tool with zero annotation coverage, this leaves significant gaps in understanding its behavior.

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

Conciseness4/5

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

The description is two concise sentences in Spanish that efficiently convey the tool's purpose and a key constraint. It's front-loaded with the main action and avoids unnecessary elaboration. However, the translation aspect might add minor complexity for non-Spanish-speaking agents, though the content itself is well-structured.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool has no parameters, no annotations, and no output schema, the description provides basic purpose and usage constraints but lacks details on behavioral aspects like response format, error handling, or operational limits. For a simple list operation, this is minimally adequate but leaves room for improvement in completeness, especially regarding what the output looks like.

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 tool has 0 parameters with 100% schema description coverage, so no parameter documentation is needed. The description appropriately doesn't discuss parameters, focusing instead on the tool's purpose and constraints. This meets the baseline expectation for a parameterless tool.

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 ('Obtiene todos los idiomas' - Gets all languages) and the resource (idiomas/languages), specifying they are for associating with activities in travel programs. It distinguishes from siblings like 'get_service_language_by_name' by indicating it retrieves all languages rather than a specific one. However, it doesn't explicitly differentiate from other list tools like 'list_services' or 'list_agencies' 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 Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage context ('para asociar a una actividad en un programa de viajes' - for associating with an activity in a travel program) and provides a constraint ('Estos idiomas solo se pueden usar para asociar a un servicio' - These languages can only be used to associate with a service). However, it doesn't explicitly state when to use this tool versus alternatives like 'get_service_language_by_name' or other list tools, nor does it mention prerequisites or exclusions.

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