Skip to main content
Glama
lumile

LumbreTravel MCP Server

by lumile

list_services

Retrieve all available services to associate with activities in travel programs. This tool helps users access and manage service options for travel planning.

Instructions

Obtiene todos los servicios disponibles para asociar a una actividad en un programa de viajes

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Schema definition for the 'list_services' tool, including name, description, and empty input schema (no parameters required). This is returned by listTools().
      name: 'list_services',
      description: 'Obtiene todos los servicios disponibles para asociar a una actividad en un programa de viajes',
      inputSchema: {
        type: 'object',
        properties: {}
      }
    },
  • Handler logic for 'list_services' tool in callTool method. Fetches all services using ApiService.getServices() and returns them as formatted JSON text response.
    case 'list_services': {
      const services = await this.apiService.getServices()
      return {
        content: [{
          type: 'text',
          text: JSON.stringify(services, null, 2)
        }]
      }
    }
  • ApiService.getServices() method: Makes authenticated GET request to /integrations/mcp/services endpoint and returns the list of services.
    async getServices () {
      const headers = await this.getHeaders()
      const response = await fetch(`${API_CONFIG.baseUrl}/integrations/mcp/services`, {
        method: 'GET',
        headers
      })
      return await this.handleResponse<any[]>(response)
    }
  • src/index.ts:38-47 (registration)
    MCP server request handlers registration: setRequestHandler for ListToolsRequestSchema (uses listTools() to provide tool list including list_services) and CallToolRequestSchema (dispatches to callTool() for execution).
    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?

With no annotations provided, the description carries full burden for behavioral disclosure. While it indicates this is a read operation ('Obtiene'), it doesn't address important behavioral aspects like whether this returns all services or is paginated, what format the results come in, or any authentication/rate limiting considerations. This leaves significant gaps in understanding how the tool behaves.

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 a single, efficient Spanish sentence that gets straight to the point without unnecessary words. It's appropriately sized for a simple list operation with no parameters. The only minor improvement would be front-loading the core purpose more explicitly.

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?

For a tool with no annotations and no output schema, the description is insufficiently complete. It doesn't describe what the return value looks like (list format, fields included), whether results are filtered or paginated, or any error conditions. Given the complexity of the sibling toolset and lack of structured metadata, more behavioral context is needed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has 0 parameters with 100% schema description coverage, so the schema fully documents the parameter situation. The description appropriately doesn't waste space discussing non-existent parameters. A baseline of 4 is appropriate since there's no parameter information needed or missing.

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 with a specific verb ('Obtiene' - gets) and resource ('servicios disponibles'), and specifies the context ('para asociar a una actividad en un programa de viajes'). However, it doesn't explicitly distinguish itself from sibling tools like 'get_services_by_name' or 'list_service_languages', which slightly reduces clarity.

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 some context about when to use the tool ('para asociar a una actividad en un programa de viajes'), but offers no explicit guidance on when NOT to use it or when to choose alternatives like 'get_services_by_name' for filtered searches. This leaves the agent with incomplete decision-making information.

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