Skip to main content
Glama
lumile

LumbreTravel MCP Server

by lumile

create_vehicle

Add a vehicle to the LumbreTravel system by specifying its name, description, brand, model, capacity, and provider details for travel program management.

Instructions

Crear un vehículo.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesNombre del vehículo
descriptionYesDescripción del vehículo
brandNoMarca del vehículo
modelNoModelo del vehículo
capacityNoCapacidad del vehículo
providerYes

Implementation Reference

  • MCP tool handler case that destructures arguments and calls apiService.createVehicle to execute the tool logic, returning the JSON-stringified result.
    case 'create_vehicle': {
      const { name, description, brand, model, capacity, provider } = args
      const vehicle = await this.apiService.createVehicle({ name, description, brand, model, capacity, provider })
      return {
        content: [{ type: 'text', text: JSON.stringify(vehicle, null, 2) }]
      }
  • Tool definition including name, description, and input schema for validation in listTools().
      name: 'create_vehicle',
      description: 'Crear un vehículo.',
      inputSchema: {
        type: 'object',
        properties: {
          name: { type: 'string', description: 'Nombre del vehículo' },
          description: { type: 'string', description: 'Descripción del vehículo' },
          brand: { type: 'string', description: 'Marca del vehículo' },
          model: { type: 'string', description: 'Modelo del vehículo' },
          capacity: { type: 'number', description: 'Capacidad del vehículo' },
          provider: {
            type: 'object',
            properties: {
              id: { type: 'string', description: 'ID del proveedor del vehículo.' },
              name: { type: 'string', description: 'Nombre del proveedor del vehículo' }
            }
          }
        },
        required: ['name', 'description', 'provider']
      }
    },
  • Underlying service method that performs the HTTP POST request to the LumbreTravel API endpoint for creating a vehicle.
    async createVehicle (data: {
      name: string
      description: string
      brand: string
      model: string
      capacity: number
      provider: {
        id: string
        name: string
      }
    }) {
      const headers = await this.getHeaders()
      const response = await fetch(`${API_CONFIG.baseUrl}/integrations/mcp/vehicle/create`, {
        method: 'POST',
        headers: { ...headers, 'Content-Type': 'application/json' },
        body: JSON.stringify(data)
      })
      return await this.handleResponse<any>(response)
    }
Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description must fully disclose behavioral traits. It only states 'Crear un vehículo,' which implies a write operation but reveals nothing about permissions, side effects, error handling, rate limits, or what happens on success/failure. This leaves critical behavioral aspects completely opaque.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

While concise with a single sentence, the description is under-specified rather than efficiently informative. It fails to front-load useful information, wasting its brevity on a tautological statement that doesn't help the agent understand the tool's role or behavior.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a creation tool with no annotations and no output schema, the description is severely incomplete. It doesn't explain what 'create' entails, what data is returned, or how it integrates with sibling tools like list_vehicles or delete_vehicle, leaving the agent with insufficient context for effective use.

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

Parameters3/5

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

Schema description coverage is high at 83%, with all parameters documented in the schema, so the baseline is 3. The description adds no additional meaning about parameters beyond what the schema provides, such as explaining relationships between fields or usage examples, but it doesn't need to compensate for gaps.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Crear un vehículo' (Create a vehicle) is a tautology that merely restates the tool name in Spanish, providing no additional specificity about what 'create' entails or what distinguishes it from other creation tools like create_agency or create_program. It fails to clarify the verb+resource relationship beyond the obvious.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description offers no guidance on when to use this tool versus alternatives, such as update_vehicle or list_vehicles, nor does it mention prerequisites, dependencies, or contextual constraints. Without any usage instructions, the agent must infer everything from the tool name alone.

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