Skip to main content
Glama
lumile

LumbreTravel MCP Server

by lumile

delete_program

Remove a travel program from the LumbreTravel system by specifying its unique identifier. This action permanently deletes the selected program and its associated data.

Instructions

Elimina un programa de viajes

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes

Implementation Reference

  • The execution handler for the 'delete_program' tool. It extracts the program ID from arguments, calls ApiService.deleteProgram(id), and returns the JSON-stringified response.
    case 'delete_program': {
      const { id } = args as { id: string }
      const program = await this.apiService.deleteProgram(id)
      return {
        content: [{ type: 'text', text: JSON.stringify(program, null, 2) }]
      }
    }
  • The input schema and metadata definition for the 'delete_program' tool, requiring a string 'id'.
    {
      name: 'delete_program',
      description: 'Elimina un programa de viajes',
      inputSchema: {
        type: 'object',
        properties: {
          id: { type: 'string' }
        },
        required: ['id']
      }
    },
  • src/index.ts:37-49 (registration)
    Registers the tool handlers on the MCP server by setting request handlers for listing tools (via ToolsHandler.listTools) and calling tools (via ToolsHandler.callTool). This indirectly registers 'delete_program'.
      // 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)
      )
    }
  • Helper method in ApiService that performs the HTTP DELETE request to the backend API to delete a program by ID.
    async deleteProgram (id: string) {
      const headers = await this.getHeaders()
      const response = await fetch(`${API_CONFIG.baseUrl}/integrations/mcp/programs/delete/${id}`, {
        method: 'DELETE',
        headers
      })
      return await this.handleResponse<any>(response)
    }
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. 'Elimina' implies a destructive operation, but it doesn't specify if deletion is permanent, reversible (e.g., via reactivate_program), requires specific permissions, or has side effects (e.g., cascading deletions). This leaves critical behavioral traits undocumented.

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 action without unnecessary words. It's appropriately sized and front-loaded, making it easy to parse quickly.

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 the tool's destructive nature (implied by 'delete'), lack of annotations, 0% schema coverage, no output schema, and multiple sibling tools, the description is incomplete. It doesn't address behavioral risks, parameter meaning, or usage context, making it inadequate for safe and effective tool invocation.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must compensate for parameter documentation. It mentions no parameters at all, failing to explain that 'id' is required or what it represents (e.g., a program identifier). This leaves the single required parameter undocumented in both schema and description.

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 'Elimina un programa de viajes' clearly states the action (elimina/delete) and resource (programa de viajes/travel program), making the purpose specific and understandable. However, it doesn't explicitly differentiate from sibling tools like delete_activities or delete_agency, which follow similar naming patterns but target different resources.

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 no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing an existing program ID), exclusions, or compare it to related tools like reactivate_program or update_program, leaving usage context unclear.

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