Skip to main content
Glama
lumile

LumbreTravel MCP Server

by lumile

get_programs_by_name

Search for travel programs by name to find specific offerings within the LumbreTravel MCP Server. This tool helps users locate programs using exact or partial name matches.

Instructions

Busca programas de viajes por nombre

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesNombre del programa

Implementation Reference

  • The handler logic in callTool method that executes the tool: extracts the 'name' parameter, calls the ApiService.getProgramsByName method, and returns the result as a text content block with JSON stringified data.
    case 'get_programs_by_name': {
      const { name } = args as { name: string }
      const program = await this.apiService.getProgramsByName(name)
      return {
        content: [{
          type: 'text',
          text: JSON.stringify(program, null, 2)
        }]
      }
  • The tool definition including name, description, and input schema (object with required 'name' string property) in the listTools() method.
    name: 'get_programs_by_name',
    description: 'Busca programas de viajes por nombre',
    inputSchema: {
      type: 'object',
      properties: {
        name: {
          type: 'string',
          description: 'Nombre del programa'
        }
      },
      required: ['name']
    }
  • Supporting utility method in ApiService that sends a POST request to the backend API endpoint '/integrations/mcp/programs/get_programs_by_name' with the 'name' parameter, using authentication headers, and handles the response.
    async getProgramsByName (name: string) {
      const headers = await this.getHeaders()
      const dataToSend = new URLSearchParams({
        name
      })
      const response = await fetch(`${API_CONFIG.baseUrl}/integrations/mcp/programs/get_programs_by_name`, {
        method: 'POST',
        headers,
        body: dataToSend
      })
      return await this.handleResponse<any>(response)
  • src/index.ts:44-47 (registration)
    Server request handler registration for CallToolRequestSchema, which routes tool calls to toolsHandler.callTool, enabling execution of get_programs_by_name among others. ListToolsRequestSchema is also registered to expose the tool list.
    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. It states it's a search operation, implying read-only behavior, but doesn't disclose critical traits like authentication needs, rate limits, pagination, or return format. For a search tool with zero annotation coverage, this leaves significant behavioral gaps.

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 directly states the tool's function. It's front-loaded with the core action and resource, with zero wasted words. Every element earns its place.

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, no output schema, and a simple parameter, the description is incomplete. It lacks behavioral context (e.g., search scope, result format) and usage guidelines. While concise, it doesn't provide enough information for the agent to fully understand the tool's operation and constraints.

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?

Schema description coverage is 100%, with the parameter 'name' fully documented in the schema. The description adds no additional meaning beyond implying name-based filtering. With high schema coverage, the baseline is 3, as the description doesn't compensate but doesn't need to heavily.

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 'Busca programas de viajes por nombre' clearly states the action (busca/search) and resource (programas de viajes/travel programs) with a specific filter (por nombre/by name). It distinguishes from siblings like 'get_program' (singular) and 'get_programs_by_date_range' (different filter), but doesn't explicitly contrast them. The purpose is specific and actionable.

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 like 'get_program' or 'get_programs_by_date_range'. The description implies usage for name-based searches, but lacks explicit context, prerequisites, or exclusions. Without this, the agent must infer usage from naming patterns alone.

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