Skip to main content
Glama
lumile

LumbreTravel MCP Server

by lumile

list_agencies

Retrieve available travel agencies to associate with travel programs using the LumbreTravel MCP Server.

Instructions

Obtiene todas las agencias disponibles para asociar a un programa de viajes

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler logic for the 'list_agencies' tool: fetches agencies using ApiService and returns JSON-formatted response.
    case 'list_agencies': {
      const agencies = await this.apiService.getAgencies()
      return {
        content: [{
          type: 'text',
          text: JSON.stringify(agencies, null, 2)
        }]
      }
    }
  • Input schema definition for the 'list_agencies' tool (no parameters required).
      name: 'list_agencies',
      description: 'Obtiene todas las agencias disponibles para asociar a un programa de viajes',
      inputSchema: {
        type: 'object',
        properties: {}
      }
    },
  • ApiService method getAgencies() that performs the HTTP GET request to retrieve the list of agencies from the backend API.
    async getAgencies () {
      const headers = await this.getHeaders()
      const response = await fetch(`${API_CONFIG.baseUrl}/integrations/mcp/agencies`, {
        method: 'GET',
        headers
      })
      return await this.handleResponse<any[]>(response)
    }
  • src/index.ts:44-47 (registration)
    Registration of the CallToolRequestHandler which dispatches to ToolsHandler.callTool based on tool name, including 'list_agencies'.
    this.server.setRequestHandler(
      CallToolRequestSchema,
      async (request) => await this.toolsHandler.callTool(request.params.name, request.params.arguments, this.server)
    )
  • src/index.ts:39-41 (registration)
    Registration of ListToolsRequestHandler which returns the list of available tools, including 'list_agencies'.
      ListToolsRequestSchema,
      async () => this.toolsHandler.listTools()
    )
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 it 'gets all available agencies' but doesn't disclose behavioral traits like whether this is a read-only operation, if it requires authentication, potential rate limits, pagination behavior, or what 'available' means (e.g., active vs. all). For a list operation with zero annotation coverage, 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.

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 any fluff or unnecessary details. It's front-loaded with the core action and resource, making it easy to parse. Every word earns its place by contributing to understanding the tool's function.

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 as a minimum viable explanation. It covers the basic purpose but lacks details on behavior, output format, or usage context that would be helpful for an AI agent. Without annotations or output schema, more guidance on what 'gets all' returns would improve completeness.

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. It adds context about the purpose ('para asociar a un programa de viajes') which provides semantic value beyond the schema. Baseline for 0 params is 4, and the description meets this by being relevant without redundancy.

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 verb 'obtiene' (gets) and the resource 'agencias disponibles' (available agencies) with the purpose 'para asociar a un programa de viajes' (to associate with a travel program). It distinguishes from siblings like 'get_agency_by_name' which filters by name, but doesn't explicitly contrast with all list_* siblings. The Spanish language is clear but not perfectly specific about scope.

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 minimal guidance: it implies usage when needing agencies for travel program association. However, it doesn't specify when to use this versus alternatives like 'get_agency_by_name' for filtered lookup, or 'create_agency' for adding new agencies. No explicit when-not-to-use or prerequisite information is given.

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