Skip to main content
Glama
lumile

LumbreTravel MCP Server

by lumile

get_services_by_name

Search for travel services by name to find available options in the LumbreTravel system. Returns matching services for planning and management.

Instructions

Buscar servicios por su nombre, retorna la lista de servicios encontrados.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesNombre del servicio

Implementation Reference

  • The execution handler for the 'get_services_by_name' MCP tool. Extracts the 'name' argument and delegates to ApiService.getServicesByName, returning the result as a text content block.
    case 'get_services_by_name': {
      const { name } = args as { name: string }
      const service = await this.apiService.getServicesByName(name)
      return {
        content: [{ type: 'text', text: JSON.stringify(service, null, 2) }]
      }
    }
  • Registration of the 'get_services_by_name' tool within the listTools() response, defining its name, description, and input schema.
    {
      name: 'get_services_by_name',
      description: 'Buscar servicios por su nombre, retorna la lista de servicios encontrados.',
      inputSchema: { type: 'object', properties: { name: { type: 'string', description: 'Nombre del servicio' } }, required: ['name'] }
    }
  • Helper method in ApiService that implements the core logic by making a POST request to the backend endpoint '/integrations/mcp/service/get_services_by_name' with the service name.
    async getServicesByName (name: string) {
      const headers = await this.getHeaders()
      const response = await fetch(`${API_CONFIG.baseUrl}/integrations/mcp/service/get_services_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?

No annotations are provided, so the description carries the full burden. It states the tool searches and returns a list, but lacks details on behavioral traits such as whether it's a read-only operation, if it requires authentication, how it handles no matches (e.g., empty list or error), rate limits, or pagination. The description is minimal and does not compensate for the absence of annotations.

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 that front-loads the purpose and outcome. It uses no unnecessary words, making it highly concise and well-structured for quick understanding.

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's low complexity (single parameter, no output schema, no annotations), the description is minimally adequate. It covers the basic action and result but lacks completeness in behavioral context, usage guidelines, and output details (e.g., what the returned list contains). For a simple search tool, it meets the minimum viable threshold but has clear gaps.

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 servicio' (Name of the service). The description adds no additional meaning beyond this, as it only repeats that it searches by name without specifying format, case-sensitivity, or partial matching. With high schema coverage, the baseline score of 3 is appropriate.

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 tool's purpose: 'Buscar servicios por su nombre' (Search services by their name) and 'retorna la lista de servicios encontrados' (returns the list of services found). It specifies the verb (search) and resource (services), but does not distinguish it from sibling tools like 'list_services' or 'get_programs_by_name', which follow a similar 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?

The description provides no guidance on when to use this tool versus alternatives. It does not mention sibling tools like 'list_services' (which might list all services without filtering) or other 'get_*_by_name' tools for different resources, nor does it specify any prerequisites or exclusions for usage.

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