Skip to main content
Glama
lumile

LumbreTravel MCP Server

by lumile

get_program

Retrieve a travel program by its ID to access itinerary details, activities, and management information from the LumbreTravel API.

Instructions

Obtiene un programa de viajes por ID

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesID del programa

Implementation Reference

  • The handler logic for the 'get_program' tool within the callTool switch statement. Extracts the 'id' from arguments, calls apiService.getProgram(id), and returns the program data as formatted JSON text content.
    case 'get_program': {
      const { id } = args as { id: string }
      const program = await this.apiService.getProgram(id)
      return {
        content: [{
          type: 'text',
          text: JSON.stringify(program, null, 2)
        }]
      }
    }
  • The tool definition including name, description, and input schema requiring a string 'id' for get_program.
    {
      name: 'get_program',
      description: 'Obtiene un programa de viajes por ID',
      inputSchema: {
        type: 'object',
        properties: {
          id: {
            type: 'string',
            description: 'ID del programa'
          }
        },
        required: ['id']
      }
    },
  • The supporting API service method that fetches the program data by ID from the backend API endpoint /integrations/mcp/programs/get/{id}.
    async getProgram (id: string) {
      const headers = await this.getHeaders()
      const response = await fetch(`${API_CONFIG.baseUrl}/integrations/mcp/programs/get/${id}`, {
        method: 'GET',
        headers
      })
      return await this.handleResponse<any>(response)
    }
  • src/index.ts:38-47 (registration)
    Registers the MCP request handlers for listing tools (listTools) and calling tools (callTool), which includes the get_program tool.
    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 states it 'gets' a program, implying a read-only operation, but doesn't disclose behavioral traits like whether it returns full details, error handling for invalid IDs, authentication needs, rate limits, or data format. For a retrieval tool with zero annotation coverage, this is a significant gap in transparency.

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 purpose. It's front-loaded with the key action and resource, with no wasted words or redundant information, making it easy to parse quickly.

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 the complexity of a retrieval tool with no annotations and no output schema, the description is incomplete. It doesn't explain what data is returned (e.g., program details, structure), error conditions, or how it fits into the broader context of sibling tools. For a tool in a system with many create/update/delete operations, more guidance on its role is needed.

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 'id' parameter documented as 'ID del programa'. The description adds no additional meaning beyond this, as it only mentions 'por ID' without specifying format, constraints, or examples. With high schema coverage, the baseline is 3, and the description doesn't compensate with extra insights.

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 verb ('Obtiene' - gets) and resource ('un programa de viajes' - a travel program) with the specific identifier ('por ID' - by ID). It distinguishes from siblings like 'get_programs_by_name' or 'get_programs_by_date_range' by specifying ID-based retrieval. However, it doesn't explicitly mention what 'programa de viajes' entails beyond the name.

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. With siblings like 'get_programs_by_name', 'get_programs_by_date_range', and 'list_providers', the description lacks context on prerequisites (e.g., needing the ID first) or comparisons to other retrieval methods. It implies usage by ID only but doesn't state this explicitly.

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