Skip to main content
Glama
lumile

LumbreTravel MCP Server

by lumile

season_summary

Generate passenger summaries for travel seasons to analyze distribution across agencies and calculate total passenger counts.

Instructions

Obtiene un resumen de pasajeros a lo largo de una temporada. Esta tool es muy útil para obtener el total de pasajeros de una temporada y ver como se distribuye por agencias.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
startYearYesAño de inicio de la temporada (YYYY)
endYearYesAño de fin de la temporada (YYYY)

Implementation Reference

  • Handler implementation for the 'season_summary' tool in the callTool method. Extracts parameters and delegates to ApiService.getSeasonSummary, returning the JSON response.
    case 'season_summary': {
      const { startYear, endYear } = args as { startYear: string, endYear: string }
      const seasonSummary = await this.apiService.getSeasonSummary(startYear, endYear)
      return {
        content: [{ type: 'text', text: JSON.stringify(seasonSummary, null, 2) }]
      }
    }
  • Input schema definition for the 'season_summary' tool in the listTools method.
      name: 'season_summary',
      description: 'Obtiene un resumen de pasajeros a lo largo de una temporada.  Esta tool es muy útil para obtener el total de pasajeros de una temporada y ver como se distribuye por agencias.',
      inputSchema: {
        type: 'object',
        properties: {
          startYear: { type: 'string', description: 'Año de inicio de la temporada (YYYY)' },
          endYear: { type: 'string', description: 'Año de fin de la temporada (YYYY)' }
        },
        required: ['startYear', 'endYear']
      }
    },
  • src/index.ts:44-47 (registration)
    Registration of the callTool handler from ToolsHandler, which dispatches to specific tool implementations including 'season_summary'.
    this.server.setRequestHandler(
      CallToolRequestSchema,
      async (request) => await this.toolsHandler.callTool(request.params.name, request.params.arguments, this.server)
    )
  • src/index.ts:38-41 (registration)
    Registration of the listTools method from ToolsHandler, which includes the 'season_summary' tool definition.
    this.server.setRequestHandler(
      ListToolsRequestSchema,
      async () => this.toolsHandler.listTools()
    )
  • Helper method in ApiService that performs the actual API call to retrieve season summary data, used by the tool handler.
    async getSeasonSummary (startYear: string, endYear: string) {
      const headers = await this.getHeaders()
      const dataToSend = new URLSearchParams({
        startYear,
        endYear
      })
      const response = await fetch(`${API_CONFIG.baseUrl}/integrations/mcp/programs/season_summary`, {
        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 mentions the tool 'es muy útil' (is very useful) but doesn't disclose critical behavioral traits such as whether it's a read-only operation, what format the summary returns (e.g., aggregated counts, breakdowns), if there are rate limits, or authentication requirements. The description adds minimal value beyond the basic purpose.

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 two sentences, front-loaded with the core purpose and followed by a utility statement. It avoids unnecessary fluff, but the second sentence ('Esta tool es muy útil...') is somewhat redundant and could be more informative about output or usage instead of just stating it's useful.

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 no annotations and no output schema, the description is incomplete for a tool that presumably returns complex aggregated data. It mentions a summary with total passengers and agency distribution, but doesn't detail the return format, potential errors, or data scope limitations. This leaves gaps for an AI agent to understand the full context of use.

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 clear parameter definitions for 'startYear' and 'endYear'. The description doesn't add any additional semantic context about these parameters beyond what's in the schema (e.g., it doesn't explain season boundaries or date format nuances), so it meets the baseline of 3 for high schema coverage without extra value.

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: 'Obtiene un resumen de pasajeros a lo largo de una temporada' (Gets a summary of passengers throughout a season). It specifies the verb (obtiene/gets) and resource (resumen de pasajeros/passenger summary), but doesn't explicitly differentiate it from sibling tools like 'get_passengers_by_email' or 'get_programs_by_date_range' which might also retrieve passenger data.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage context with 'para obtener el total de pasajeros de una temporada y ver como se distribuye por agencias' (to get the total passengers for a season and see how they are distributed by agencies), suggesting it's for aggregated seasonal analysis. However, it doesn't provide explicit guidance on when to use this versus alternatives like 'get_programs_by_date_range' or 'list_agencies', nor does it mention any prerequisites 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