Skip to main content
Glama
lumile

LumbreTravel MCP Server

by lumile

delete_service_language

Remove a service language from the LumbreTravel MCP Server by specifying its ID to manage multilingual content for travel programs and activities.

Instructions

Eliminar un idioma de servicio.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesID del idioma de servicio a eliminar

Implementation Reference

  • Registration of the 'delete_service_language' tool including its name, description, and input schema in the listTools method.
    {
      name: 'delete_service_language',
      description: 'Eliminar un idioma de servicio.',
      inputSchema: {
        type: 'object',
        properties: { id: { type: 'string', description: 'ID del idioma de servicio a eliminar' } },
        required: ['id']
      }
  • Input schema definition for the 'delete_service_language' tool.
    inputSchema: {
      type: 'object',
      properties: { id: { type: 'string', description: 'ID del idioma de servicio a eliminar' } },
      required: ['id']
    }
  • Execution handler for the 'delete_service_language' tool in the callTool switch statement, which invokes the ApiService method.
    case 'delete_service_language': {
      const { id } = args as { id: string }
      const serviceLanguage = await this.apiService.deleteServiceLanguage(id)
      return {
        content: [{ type: 'text', text: JSON.stringify(serviceLanguage, null, 2) }]
      }
    }
  • Supporting ApiService method that performs the HTTP DELETE request to the backend API to delete a service language by ID.
    async deleteServiceLanguage (id: string) {
      const headers = await this.getHeaders()
      const response = await fetch(`${API_CONFIG.baseUrl}/integrations/mcp/servicelanguage/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. While 'Eliminar' implies a destructive operation, it doesn't specify whether deletion is permanent or reversible, what permissions are required, or what happens to associated data. For a mutation tool with zero annotation coverage, this leaves significant behavioral gaps.

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 Spanish sentence ('Eliminar un idioma de servicio') that directly states the tool's purpose with zero wasted words. It's appropriately sized for a simple deletion operation and front-loads the essential information.

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 operation with no annotations and no output schema, the description is insufficient. It doesn't explain what 'eliminar' entails (permanent vs soft delete), what confirmation or side effects exist, or what the tool returns. Given the complexity of deletion in a system with 'reactivate' tools, more context is needed.

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' clearly documented in the schema as 'ID del idioma de servicio a eliminar'. The description adds no additional parameter information beyond what the schema provides, so it meets the baseline of 3 for high schema 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 clearly states the action ('Eliminar' meaning 'Delete') and the resource ('idioma de servicio' meaning 'service language'), providing a specific verb+resource combination. However, it doesn't differentiate from sibling tools like 'delete_service' or 'reactivate_service_language', which would require more specificity to earn a 5.

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 like 'reactivate_service_language' (which appears to restore deleted items) or other deletion tools. There's no mention of prerequisites, consequences, or appropriate contexts for deletion versus other 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