Skip to main content
Glama
lumile

LumbreTravel MCP Server

by lumile

update_agency

Modify travel agency details including name, description, and provider information within the LumbreTravel system to maintain accurate program data.

Instructions

Actualizar una agencia

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesID de la agencia a actualizar
nameYesNombre de la agencia
descriptionYesDescripción de la agencia
providerYes

Implementation Reference

  • Handler logic in callTool method that processes arguments and invokes the ApiService updateAgency method, returning the result as MCP content.
    case 'update_agency': {
      const { id, name, description, provider } = args
      const agency = await this.apiService.updateAgency({ id, name, description, provider })
      return {
        content: [{ type: 'text', text: JSON.stringify(agency, null, 2) }]
      }
    }
  • Tool definition including name, description, and input schema for validation in listTools().
      name: 'update_agency',
      description: 'Actualizar una agencia',
      inputSchema: {
        type: 'object',
        properties: {
          id: { type: 'string', description: 'ID de la agencia a actualizar' },
          name: { type: 'string', description: 'Nombre de la agencia' },
          description: { type: 'string', description: 'Descripción de la agencia' },
          provider: {
            type: 'object',
            properties: {
              id: { type: 'string', description: 'ID del proveedor de la agencia' },
              name: { type: 'string', description: 'Nombre del proveedor de la agencia' }
            }
          }
        },
        required: ['id', 'name', 'description', 'provider']
      }
    },
  • ApiService method that performs the HTTP PUT request to update an agency using authenticated headers and error handling.
    async updateAgency (data: {
      id: string
      name: string
      description: string
      provider: {
        id: string
        name: string
      }
    }) {
      const headers = await this.getHeaders()
      const response = await fetch(`${API_CONFIG.baseUrl}/integrations/mcp/agency/update`, {
        method: 'PUT',
        headers: { ...headers, 'Content-Type': 'application/json' },
        body: JSON.stringify(data)
      })
      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 the full burden of behavioral disclosure. 'Actualizar una agencia' only indicates it's a mutation operation but provides no information about permissions required, whether changes are reversible, what happens to existing data not mentioned in parameters, error conditions, or what the tool returns. For a mutation tool with zero annotation coverage, this is a significant gap in behavioral transparency.

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 extremely concise at just two words ('Actualizar una agencia'), which could be appropriate if it were more informative. However, this brevity comes at the cost of being under-specified rather than efficiently informative. It's front-loaded but lacks the necessary content to be truly helpful.

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?

Given this is a mutation tool with 4 required parameters (including a nested object), no annotations, and no output schema, the description is completely inadequate. It doesn't explain what the tool does beyond the basic verb, provides no behavioral context, offers no parameter guidance, and gives no indication of what happens after invocation. For a tool with this complexity and lack of structured metadata, the description should do much more.

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 75%, meaning most parameters have descriptions in the schema itself. The tool description adds no information about parameters beyond what's already in the schema. It doesn't explain the relationship between parameters, provide examples, or clarify semantics like what constitutes a valid 'provider' object. With 4 parameters and no parameter information in the description, it fails to compensate for the 25% coverage gap.

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 'Actualizar una agencia' (Update an agency) is a tautology that merely restates the tool name in Spanish. It doesn't specify what aspects of an agency can be updated, what the operation entails, or how it differs from sibling tools like 'create_agency' or 'reactivate_agency'. While it indicates a basic action, it lacks specificity and differentiation.

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?

The description provides no guidance on when to use this tool versus alternatives. There are multiple sibling tools for agency operations (create_agency, delete_agency, reactivate_agency, list_agencies, get_agency_by_name), but the description doesn't indicate when this update operation is appropriate versus creating a new agency or reactivating a deleted one. No prerequisites, constraints, or contextual usage information is provided.

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