Skip to main content
Glama
lumile

LumbreTravel MCP Server

by lumile

delete_agency

Remove a travel agency from the LumbreTravel system to prevent its association with programs.

Instructions

Eliminar una agencia. La agencia eliminada no se puede usar para asociarle programas

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesID de la agencia a eliminar

Implementation Reference

  • Handler logic in callTool method that executes the delete_agency tool by calling ApiService.deleteAgency(id) and returning the result.
    case 'delete_agency': {
      const { id } = args as { id: string }
      const agency = await this.apiService.deleteAgency(id)
      return {
        content: [{ type: 'text', text: JSON.stringify(agency, null, 2) }]
      }
    }
  • Registration of the delete_agency tool in the listTools() method's tools array, including name, description, and input schema.
    {
      name: 'delete_agency',
      description: 'Eliminar una agencia.  La agencia eliminada no se puede usar para asociarle programas',
      inputSchema: {
        type: 'object',
        properties: {
          id: { type: 'string', description: 'ID de la agencia a eliminar' }
        },
        required: ['id']
      }
    },
  • Input schema for the delete_agency tool, defining required 'id' parameter.
    inputSchema: {
      type: 'object',
      properties: {
        id: { type: 'string', description: 'ID de la agencia a eliminar' }
      },
      required: ['id']
    }
  • ApiService helper method that performs the actual API call to delete an agency by ID.
    async deleteAgency (id: string) {
      const headers = await this.getHeaders()
      const response = await fetch(`${API_CONFIG.baseUrl}/integrations/mcp/agency/delete/${id}`, {
        method: 'DELETE',
        headers
      })
      return await this.handleResponse<any>(response)
    }
Behavior3/5

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

With no annotations provided, the description carries full burden. It discloses the destructive nature ('eliminar') and a key consequence ('no se puede usar para asociarle programas'), which is valuable behavioral context. However, it doesn't mention permissions needed, whether deletion is reversible, or what happens to associated data beyond programs.

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 two concise sentences that efficiently convey the core action and a critical consequence. It's appropriately sized for a destructive operation, though it could be slightly more structured by explicitly separating action from implications.

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

Completeness3/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 provides basic but incomplete context. It covers the irreversible consequence regarding programs but lacks details about permissions, error conditions, return values, or broader system impacts, leaving gaps for agent understanding.

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 the single parameter 'id' well-documented in the schema. The description doesn't add any parameter-specific information beyond what the schema provides, so it meets the baseline of 3 for high schema coverage without compensating value.

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

Purpose5/5

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

The description clearly states the action ('eliminar' - delete) and resource ('una agencia'), making the purpose specific and unambiguous. It distinguishes this tool from siblings like 'create_agency', 'update_agency', 'reactivate_agency', and 'list_agencies' by focusing on permanent removal.

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

Usage Guidelines3/5

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

The description implies usage context by stating the agency cannot be used for programs after deletion, suggesting this is for permanent removal when an agency is no longer needed. However, it doesn't explicitly state when to use this versus alternatives like 'reactivate_agency' or provide clear exclusions.

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