Skip to main content
Glama
lumile

LumbreTravel MCP Server

by lumile

daily_activities

Retrieve daily travel activities by date with optional filters for hotels, guides, services, or vehicles to manage travel programs.

Instructions

Obtiene las actividades diarias

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dateYesFecha en la que buscar las actividades (DD-MM-YYYY)
hotelIdToFilterNoID del hotel a filtrar las actividades, si no se especifica se obtienen todas las actividades
leaderIdToFilterNoID del guía a filtrar las actividades, si no se especifica se obtienen todas las actividades
serviceIdToFilterNoID del servicio a filtrar las actividades, si no se especifica se obtienen todas las actividades
vehicleIdToFilterNoID del vehículo a filtrar las actividades, si no se especifica se obtienen todas las actividades

Implementation Reference

  • The execution handler for the 'daily_activities' tool. Extracts arguments and delegates to ApiService.getDailyActivities, then returns the JSON response.
    case 'daily_activities': {
      const { date, hotelIdToFilter, leaderIdToFilter, vehicleIdToFilter, serviceIdToFilter } = args as { date: string, hotelIdToFilter: string, leaderIdToFilter: string, vehicleIdToFilter: string, serviceIdToFilter: string }
      const activities = await this.apiService.getDailyActivities(date, hotelIdToFilter, leaderIdToFilter, vehicleIdToFilter, serviceIdToFilter)
      return {
        content: [{ type: 'text', text: JSON.stringify(activities, null, 2) }]
      }
    }
  • Input schema and tool definition for 'daily_activities' returned by listTools method.
      name: 'daily_activities',
      description: 'Obtiene las actividades diarias',
      inputSchema: {
        type: 'object',
        properties: {
          date: {
            type: 'string',
            description: 'Fecha en la que buscar las actividades (DD-MM-YYYY)'
          },
          hotelIdToFilter: {
            type: 'string',
            description: 'ID del hotel a filtrar las actividades, si no se especifica se obtienen todas las actividades'
          },
          leaderIdToFilter: {
            type: 'string',
            description: 'ID del guía a filtrar las actividades, si no se especifica se obtienen todas las actividades'
          },
          serviceIdToFilter: {
            type: 'string',
            description: 'ID del servicio a filtrar las actividades, si no se especifica se obtienen todas las actividades'
          },
          vehicleIdToFilter: {
            type: 'string',
            description: 'ID del vehículo a filtrar las actividades, si no se especifica se obtienen todas las actividades'
          }
        },
        required: ['date']
      }
    },
  • ApiService method that performs the HTTP POST request to fetch daily activities from the backend API endpoint.
    async getDailyActivities (date: string, hotelIdToFilter: string, leaderIdToFilter: string, vehicleIdToFilter: string, serviceIdToFilter: string) {
      const dateForDailyActivities = convertToISOWithOffset(date)
      const headers = await this.getHeaders()
      const dataToSend = new URLSearchParams({
        date: dateForDailyActivities,
        hotelIdToFilter,
        leaderIdToFilter,
        vehicleIdToFilter,
        serviceIdToFilter
      })
      const response = await fetch(`${API_CONFIG.baseUrl}/integrations/mcp/programs/daily_activities`, {
        method: 'POST',
        headers,
        body: dataToSend
      })
      return await this.handleResponse<any>(response)
    }
  • src/index.ts:38-47 (registration)
    MCP server request handlers are registered for ListToolsRequestSchema (which includes daily_activities schema) and CallToolRequestSchema (which dispatches to the tool handler).
    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 full burden. It states a read operation ('obtiene'), implying it's likely non-destructive, but doesn't disclose behavioral traits such as authentication needs, rate limits, pagination, or what the return format looks like. This is inadequate for a tool with 5 parameters and no output schema.

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 unnecessary words. It's appropriately sized and front-loaded, with zero waste.

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 (5 parameters, no annotations, no output schema), the description is incomplete. It doesn't explain the return values, error conditions, or how filtering works beyond what's in the schema. For a tool that likely returns structured activity data, this leaves significant gaps for an AI agent.

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 each parameter clearly documented in the input schema. The description adds no additional meaning beyond the schema, such as explaining relationships between filters or default behaviors. Baseline 3 is appropriate since the schema does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Obtiene las actividades diarias' (Gets the daily activities) states a clear verb ('obtiene') and resource ('actividades diarias'), but it's vague about scope and doesn't distinguish from sibling tools like 'get_program' or 'get_programs_by_date_range'. It lacks specificity about what 'daily activities' entails in this context.

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 many sibling tools like 'get_program' or 'get_programs_by_date_range', the description doesn't clarify if this is for filtered activity listings versus broader program queries, leaving usage context implied at best.

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