Skip to main content
Glama
lumile

LumbreTravel MCP Server

by lumile

get_programs_by_date_range

Retrieve travel programs available within a specified date range to plan trips effectively.

Instructions

Obtiene programas de viajes por rango de fechas

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
startDateNoFecha de inicio del programa (DD-MM-YYYY)
endDateNoFecha de fin del programa (DD-MM-YYYY)

Implementation Reference

  • The primary handler logic for the 'get_programs_by_date_range' MCP tool. It extracts startDate and endDate from arguments, formats them using the formatDate utility, calls the ApiService method, and returns the programs as formatted JSON text content.
    case 'get_programs_by_date_range': {
      const { startDate, endDate } = args
      const programs = await this.apiService.getProgramsByDateRange(
        formatDate(startDate),
        formatDate(endDate)
      )
      return {
        content: [{
          type: 'text',
          text: JSON.stringify(programs, null, 2)
        }]
      }
    }
  • Tool registration in listTools() method, defining the name, description, and input schema for 'get_programs_by_date_range'.
    {
      name: 'get_programs_by_date_range',
      description: 'Obtiene programas de viajes por rango de fechas',
      inputSchema: {
        type: 'object',
        properties: {
          startDate: {
            type: 'string',
            description: 'Fecha de inicio del programa (DD-MM-YYYY)'
          },
          endDate: {
            type: 'string',
            description: 'Fecha de fin del programa (DD-MM-YYYY)'
          }
        }
      }
    },
  • Input schema definition for validating tool arguments: startDate and endDate as strings in DD-MM-YYYY format.
    inputSchema: {
      type: 'object',
      properties: {
        startDate: {
          type: 'string',
          description: 'Fecha de inicio del programa (DD-MM-YYYY)'
        },
        endDate: {
          type: 'string',
          description: 'Fecha de fin del programa (DD-MM-YYYY)'
        }
      }
    }
  • Supporting ApiService method that performs authenticated POST request to backend API endpoint to fetch programs by date range.
    async getProgramsByDateRange (startDate: string, endDate: string) {
      const headers = await this.getHeaders()
      const dataToSend = new URLSearchParams({
        startDate,
        endDate
      })
      const response = await fetch(`${API_CONFIG.baseUrl}/integrations/mcp/programs/get_programs_by_date_range`, {
        method: 'POST',
        headers,
        body: dataToSend
      })
      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 it retrieves programs but doesn't disclose behavioral traits like whether it's read-only (implied by 'get'), what happens if no programs match, if results are paginated, or if it requires authentication. For a retrieval tool with zero annotation coverage, this is a significant gap.

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 without redundancy. It's appropriately sized and front-loaded, with zero waste, making it highly concise and well-structured.

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 doesn't explain what 'programas de viajes' entails, the return format, or error handling. For a retrieval tool with 2 parameters, it should provide more context about behavior and results to be fully helpful.

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 both parameters ('startDate', 'endDate') fully documented in the schema. The description adds no additional meaning beyond implying date-range filtering, so it meets the baseline of 3 where the schema does the heavy lifting.

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' - gets/retrieves) and resource ('programas de viajes' - travel programs) with a specific scope ('por rango de fechas' - by date range). It distinguishes from siblings like 'get_program' (singular) and 'get_programs_by_name' (by name), though not explicitly. However, it doesn't fully differentiate from potential date-based queries in other tools, keeping it at 4.

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 like 'get_programs_by_name' or 'get_program'. It lacks context on prerequisites, such as whether date ranges must be valid or programs exist, and doesn't mention exclusions or complementary tools.

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