Skip to main content
Glama
lumile

LumbreTravel MCP Server

by lumile

list_providers

Retrieve all available providers from the LumbreTravel MCP Server to access travel programs and activities.

Instructions

Obtiene todos los proveedores disponibles

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler execution for the 'list_providers' tool: fetches providers via ApiService and returns them as a JSON text response.
    case 'list_providers': {
      const providers = await this.apiService.getProviders()
      return {
        content: [{
          type: 'text',
          text: JSON.stringify(providers, null, 2)
        }]
      }
    }
  • Input schema definition for the 'list_providers' tool: no required parameters, returns all available providers.
      name: 'list_providers',
      description: 'Obtiene todos los proveedores disponibles',
      inputSchema: {
        type: 'object',
        properties: {}
      }
    },
  • ApiService method that performs an authenticated GET request to the backend API endpoint to retrieve the list of providers.
    async getProviders () {
      const headers = await this.getHeaders()
      const response = await fetch(`${API_CONFIG.baseUrl}/integrations/mcp/providers`, {
        method: 'GET',
        headers
      })
      return await this.handleResponse<any[]>(response)
    }
  • src/index.ts:38-47 (registration)
    Registers the MCP server request handlers for listing tools (which includes list_providers) and calling tools by name.
    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') but doesn't disclose behavioral traits like whether it requires authentication, has rate limits, returns paginated results, or what format the output takes. For a tool with zero annotation coverage, this is a significant gap in transparency.

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 directly states the tool's function. It's appropriately sized for a simple tool with no parameters, though it could be slightly more informative without losing conciseness.

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 minimally adequate but incomplete. It lacks context on output format, behavioral constraints, and differentiation from siblings. For a read-only list tool, it should ideally specify return structure or usage context to be fully helpful.

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 absence of inputs. The description doesn't need to add parameter semantics, and it correctly implies no filtering parameters by stating 'todos' (all). Baseline is 4 for zero parameters with high schema coverage.

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 todos los proveedores disponibles' (Gets all available providers) clearly states the verb ('obtiene') and resource ('proveedores'), but it's vague about scope and doesn't differentiate from sibling tools like 'get_provider_by_name' or 'list_agencies' which serve similar listing functions for other entities. It specifies 'todos' (all) but lacks detail on what 'available' means or if there are filters.

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 siblings like 'get_provider_by_name' for filtered lookups and other list_* tools for different resources, the description doesn't indicate this is for unfiltered provider listings or suggest any context for choosing it over other 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