Skip to main content
Glama
lumile

LumbreTravel MCP Server

by lumile

delete_leader

Remove a guide from the travel management system by specifying their unique identifier.

Instructions

Eliminar un guía

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesID del guía a eliminar

Implementation Reference

  • Handler execution logic for the 'delete_leader' tool. Extracts the leader ID from arguments, calls apiService.deleteLeader(id), and returns the JSON-stringified result as text content.
    case 'delete_leader': {
      const { id } = args as { id: string }
      const leader = await this.apiService.deleteLeader(id)
      return {
        content: [{ type: 'text', text: JSON.stringify(leader, null, 2) }]
      }
    }
  • Tool schema definition for 'delete_leader', including name, description, and input schema requiring a string 'id'.
    {
      name: 'delete_leader',
      description: 'Eliminar un guía',
      inputSchema: { type: 'object', properties: { id: { type: 'string', description: 'ID del guía a eliminar' } }, required: ['id'] }
    },
  • src/index.ts:38-47 (registration)
    Registers the ToolsHandler's listTools and callTool methods with the MCP server for handling tool requests, effectively registering all tools including 'delete_leader'.
    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)
    )
  • Supporting API service method that performs the actual HTTP DELETE request to delete a leader by ID via the backend API.
    async deleteLeader (id: string) {
      const headers = await this.getHeaders()
      const response = await fetch(`${API_CONFIG.baseUrl}/integrations/mcp/leader/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 but only states the action ('eliminar') without behavioral details. It doesn't disclose if deletion is permanent, requires specific permissions, has side effects (e.g., cascading deletions), or returns confirmation. For a destructive operation with zero annotation coverage, this is a significant gap.

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 phrase ('Eliminar un guía') that directly conveys the tool's purpose without unnecessary words. It's appropriately sized and front-loaded, with zero wasted content.

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?

For a destructive deletion tool with no annotations and no output schema, the description is incomplete. It lacks critical context: permanence of deletion, error conditions, return values, or how it differs from reactivation tools. The schema covers the parameter, but behavioral aspects are underspecified.

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 100% with one parameter 'id' documented as 'ID del guía a eliminar'. The description adds no parameter semantics beyond what the schema provides, but the schema fully covers the single parameter, meeting the baseline for high coverage.

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 'Eliminar un guía' clearly states the action (eliminar/delete) and target resource (guía/leader) in Spanish, matching the tool name. It distinguishes from siblings like 'create_leader' and 'update_leader' by specifying deletion, but doesn't clarify what a 'guía' represents beyond the name.

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?

No guidance on when to use this tool versus alternatives like 'reactivate_leader' or other deletion tools (e.g., 'delete_agency'). The description implies it's for removing a leader, but doesn't specify prerequisites, consequences, or when deletion is appropriate versus deactivation.

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