Skip to main content
Glama
lumile

LumbreTravel MCP Server

by lumile

list_vehicles

Retrieve available vehicles to assign to travel program activities. This tool accesses the LumbreTravel API to display transport options for trip planning.

Instructions

Obtiene todos los vehículos disponibles para asociar a una actividad en un programa de viajes

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Executes the list_vehicles tool by calling ApiService.getVehicles() and formatting the response as MCP content.
    case 'list_vehicles': {
      const vehicles = await this.apiService.getVehicles()
      return {
        content: [{
          type: 'text',
          text: JSON.stringify(vehicles, null, 2)
        }]
      }
    }
  • Input schema and metadata definition for the list_vehicles tool within the listTools() response.
      name: 'list_vehicles',
      description: 'Obtiene todos los vehículos disponibles para asociar a una actividad en un programa de viajes',
      inputSchema: {
        type: 'object',
        properties: {}
      }
    },
  • ApiService method that sends a GET request to the backend API endpoint to fetch all available vehicles.
    async getVehicles () {
      const headers = await this.getHeaders()
      const response = await fetch(`${API_CONFIG.baseUrl}/integrations/mcp/vehicles`, {
        method: 'GET',
        headers
      })
      return await this.handleResponse<any[]>(response)
    }
  • src/index.ts:36-48 (registration)
    Registers the MCP server request handlers for listing tools (listTools) and calling tools (callTool), enabling the list_vehicles tool.
    private setupHandlers (): void {
      // Configure handlers to list tools
      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 the full burden of behavioral disclosure. It indicates this is a read operation ('obtiene'), but lacks details on permissions, rate limits, pagination, or return format. For a list tool with zero annotation coverage, this is insufficient to inform the agent about key behavioral traits.

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 conveys the core purpose without waste. It is appropriately sized for a simple list tool, though it could be slightly more structured (e.g., front-loading key terms).

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 no annotations, no output schema, and 0 parameters, the description is minimal. It states the purpose but lacks details on behavior, return values, or usage context relative to siblings. For a tool in a complex server with many siblings, this leaves significant gaps in helping the agent understand how to use it effectively.

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 input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description appropriately doesn't mention parameters, focusing on the tool's purpose. A baseline of 4 is applied since no parameters exist, and the description doesn't add unnecessary param info.

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/retrieves) and the resource 'vehículos disponibles' (available vehicles), specifying the purpose as retrieving vehicles for associating with activities in a travel program. However, it doesn't explicitly differentiate from sibling tools like 'get_vehicle_by_name' or 'create_vehicle', which would require a 5.

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 mentions the context 'para asociar a una actividad en un programa de viajes' (for associating with an activity in a travel program), which implies usage when vehicles are needed for activity association. However, it provides no explicit guidance on when to use this tool versus alternatives like 'get_vehicle_by_name' or 'create_vehicle', nor any exclusions or prerequisites.

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