Skip to main content
Glama
lumile

LumbreTravel MCP Server

by lumile

delete_vehicle

Remove a vehicle from the LumbreTravel system by providing its unique ID to manage travel program resources.

Instructions

Eliminar un vehículo.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesID del vehículo a eliminar

Implementation Reference

  • Handler implementation for the 'delete_vehicle' MCP tool. Extracts the vehicle ID from arguments, calls ApiService.deleteVehicle(id), and returns the JSON response.
    case 'delete_vehicle': {
      const { id } = args as { id: string }
      const vehicle = await this.apiService.deleteVehicle(id)
      return {
        content: [{ type: 'text', text: JSON.stringify(vehicle, null, 2) }]
      }
    }
  • Schema definition for the 'delete_vehicle' tool in listTools(), including input schema requiring 'id' string.
    {
      name: 'delete_vehicle',
      description: 'Eliminar un vehículo.',
      inputSchema: { type: 'object', properties: { id: { type: 'string', description: 'ID del vehículo a eliminar' } }, required: ['id'] }
    },
  • Tool registration in listTools() method, which responds to ListToolsRequestSchema.
    {
      name: 'delete_vehicle',
      description: 'Eliminar un vehículo.',
      inputSchema: { type: 'object', properties: { id: { type: 'string', description: 'ID del vehículo a eliminar' } }, required: ['id'] }
    },
  • ApiService.deleteVehicle helper method that makes DELETE request to backend API to delete vehicle by ID.
    async deleteVehicle (id: string) {
      const headers = await this.getHeaders()
      const response = await fetch(`${API_CONFIG.baseUrl}/integrations/mcp/vehicle/delete/${id}`, {
        method: 'DELETE',
        headers
      })
      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 carries full burden. It states the action (delete) but reveals nothing about behavioral traits: no mention of whether deletion is permanent, requires specific permissions, affects related data, has confirmation steps, or returns any output. For a destructive operation with zero annotation coverage, this is critically inadequate.

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

Conciseness3/5

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

The description is extremely concise (3 words) but under-specified rather than efficiently informative. While it avoids waste, it fails to provide necessary context for a destructive operation. Conciseness without substance doesn't earn high marks.

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 destructive tool with no annotations and no output schema, the description is completely inadequate. It doesn't explain consequences, return values, error conditions, or usage context. Given the complexity of deletion operations and lack of structured data, this description leaves critical gaps.

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 1 parameter with 100% description coverage ('ID del vehículo a eliminar'), so the schema fully documents the parameter. The description adds no parameter information, which is acceptable given the high schema coverage. With 0 parameters needing semantic clarification, a baseline of 4 is appropriate.

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 'Eliminar un vehículo' (Delete a vehicle) is a tautology that merely restates the tool name in Spanish. It specifies the verb (delete) and resource (vehicle), but doesn't differentiate from sibling tools like 'delete_activities' or 'delete_program' beyond the resource name. This provides minimal clarity 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?

No guidance is provided on when to use this tool versus alternatives. With sibling tools like 'reactivate_vehicle' and 'update_vehicle', the description doesn't indicate if deletion is permanent, reversible, or has prerequisites. It fails to help an agent choose between deletion and other vehicle-related operations.

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