Skip to main content
Glama
lumile

LumbreTravel MCP Server

by lumile

get_service_language_by_name

Find service languages by name to identify available language options for travel programs and activities in the LumbreTravel system.

Instructions

Buscar idiomas de servicio por su nombre.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesNombre del idioma de servicio

Implementation Reference

  • The main handler function for the 'get_service_language_by_name' MCP tool. It extracts the 'name' parameter from args, calls apiService.getServiceLanguageByName(name), and returns the result as a text content response.
    case 'get_service_language_by_name': {
      const { name } = args
      const serviceLanguage = await this.apiService.getServiceLanguageByName(name)
      return {
        content: [{ type: 'text', text: JSON.stringify(serviceLanguage, null, 2) }]
      }
    }
  • The input schema and metadata (name, description) for the 'get_service_language_by_name' tool, defined in the listTools() method.
      name: 'get_service_language_by_name',
      description: 'Buscar idiomas de servicio por su nombre.',
      inputSchema: { type: 'object', properties: { name: { type: 'string', description: 'Nombre del idioma de servicio' } }, required: ['name'] }
    },
  • The ApiService helper method that performs the actual API call to retrieve service languages by name, used by the tool handler.
    async getServiceLanguageByName (name: string) {
      const headers = await this.getHeaders()
      const response = await fetch(`${API_CONFIG.baseUrl}/integrations/mcp/servicelanguage/get_servicelanguages_by_name`, {
        method: 'POST',
        headers: { ...headers, 'Content-Type': 'application/json' },
        body: JSON.stringify({ name })
      })
      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 the full burden of behavioral disclosure. It mentions searching but doesn't specify whether this is a read-only operation, if it requires authentication, what happens on no match (e.g., returns empty or error), or any rate limits. This leaves significant gaps for a tool that likely queries a database.

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 a single, efficient sentence in Spanish that directly states the tool's function. It's front-loaded with the core action and resource, though it could be slightly more structured by including key details like output format or usage context.

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 no annotations and no output schema, the description is incomplete. It lacks details on behavioral traits (e.g., read-only nature, error handling), return values, and differentiation from siblings. For a search tool in a system with many similar 'get_by_name' tools, this leaves the agent under-informed.

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% description coverage, with the parameter 'name' documented as 'Nombre del idioma de servicio'. The description adds no additional meaning beyond this, such as format examples or search behavior (e.g., exact match vs. partial). Baseline 3 is appropriate since the schema does the heavy lifting.

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 'Buscar idiomas de servicio por su nombre' (Search service languages by their name) states the action (search) and resource (service languages) with a specific filter (by name), but it doesn't differentiate from sibling tools like 'list_service_languages' or other 'get_by_name' tools (e.g., 'get_agency_by_name'), leaving the purpose somewhat vague in context.

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 such as 'list_service_languages' for broader queries or other 'get_by_name' tools for different resources. The description implies usage for searching by name but offers no explicit context 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