Skip to main content
Glama
lumile

LumbreTravel MCP Server

by lumile

list_leaders

Retrieve available travel guides to assign to activities in travel programs. This tool helps users find and associate guides with program activities.

Instructions

Obtiene todos los guías disponibles para asociar a una actividad en un programa de viajes

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Registration of the 'list_leaders' tool in the listTools() method, including its name, description, and empty input schema (no parameters required).
      name: 'list_leaders',
      description: 'Obtiene todos los guías disponibles para asociar a una actividad en un programa de viajes',
      inputSchema: {
        type: 'object',
        properties: {}
      }
    },
  • The handler function for 'list_leaders' tool. It calls apiService.getLeaders() to fetch all leaders and returns the JSON stringified list as text content.
    case 'list_leaders': {
      const leaders = await this.apiService.getLeaders()
      return {
        content: [{
          type: 'text',
          text: JSON.stringify(leaders, null, 2)
        }]
      }
    }
  • Input schema for 'list_leaders' tool: an empty object (no required parameters).
      name: 'list_leaders',
      description: 'Obtiene todos los guías disponibles para asociar a una actividad en un programa de viajes',
      inputSchema: {
        type: 'object',
        properties: {}
      }
    },
  • Helper method getLeaders() in ApiService that performs a GET request to the backend API endpoint /integrations/mcp/leaders to retrieve the list of leaders.
    async getLeaders () {
      const headers = await this.getHeaders()
      const response = await fetch(`${API_CONFIG.baseUrl}/integrations/mcp/leaders`, {
        method: 'GET',
        headers
      })
      return await this.handleResponse<any[]>(response)
    }
  • src/index.ts:38-47 (registration)
    Top-level MCP server registration of tool handlers via ToolsHandler's listTools and callTool methods.
    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 this is a read operation ('obtiene' - gets), which implies it's non-destructive, but doesn't disclose any behavioral traits like whether it returns all guides or filtered ones, pagination, rate limits, authentication needs, or response format. For a tool with zero annotation coverage, this is a significant gap in behavioral context.

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 sentence in Spanish that states the purpose clearly. It's appropriately sized for a simple list tool with no parameters. While it could be slightly more detailed about behavior, every word contributes to understanding the tool's role.

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 the tool's simplicity (0 parameters, no output schema, no annotations), the description is adequate but has clear gaps. It explains what the tool does but lacks behavioral details like return format or any constraints. For a read-only list tool, it meets minimum viability but doesn't provide complete context for optimal agent usage.

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 (empty schema). The description doesn't need to explain parameters, and it appropriately doesn't mention any. Baseline for 0 parameters is 4, as there's nothing to compensate for and no schema burden.

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 todos los guías disponibles para asociar a una actividad en un programa de viajes' (Gets all available guides to associate with an activity in a travel program). It specifies the verb ('obtiene' - gets) and resource ('guías' - guides), and distinguishes it from siblings like 'create_leader' or 'get_leader_by_name' by focusing on listing all guides. However, it doesn't explicitly differentiate from other list tools like 'list_agencies' beyond the resource type.

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: when you need to associate guides with activities in travel programs. It suggests this is for selection purposes, but doesn't explicitly state when to use this vs. alternatives like 'get_leader_by_name' for specific lookups or 'create_leader' for adding new guides. No explicit exclusions or prerequisites are mentioned.

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