Skip to main content
Glama
lumile

LumbreTravel MCP Server

by lumile

update_include

Modify travel program extras or inclusions by updating their ID, name, and description details.

Instructions

Actualizar un extra o incluído.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesID a actualizar
nameYesNombre
descriptionYesDescripción

Implementation Reference

  • Executes the update_include MCP tool. Destructures id, name, description from args, calls apiService.updateInclude, and formats the response as MCP content.
    case 'update_include': {
      const { id, name, description } = args
      const include = await this.apiService.updateInclude({ id, name, description })
      return {
        content: [{ type: 'text', text: JSON.stringify(include, null, 2) }]
      }
  • Registers the 'update_include' tool in the listTools() response, including name, description, and input schema.
    name: 'update_include',
    description: 'Actualizar un extra o incluído.',
    inputSchema: {
      type: 'object',
      properties: {
        id: { type: 'string', description: 'ID a actualizar' },
        name: { type: 'string', description: 'Nombre' },
        description: { type: 'string', description: 'Descripción' }
      },
      required: ['id', 'name', 'description']
    }
  • Helper method in ApiService that sends a PUT request to the LumbreTravel API endpoint /integrations/mcp/include/update to perform the include update.
    async updateInclude (data: {
      id: string
      name: string
      description: string
    }) {
      const headers = await this.getHeaders()
      const response = await fetch(`${API_CONFIG.baseUrl}/integrations/mcp/include/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?

With no annotations provided, the description carries the full burden of behavioral disclosure but provides almost none. 'Actualizar' implies a mutation operation, but there's no information about permissions required, whether this is a partial or complete update, what validation occurs, whether changes are reversible, error conditions, or what the response contains. For a mutation tool with zero annotation coverage, this represents a significant transparency gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

While technically concise with just one Spanish sentence, this represents under-specification rather than effective brevity. The description is too minimal to be helpful - it doesn't provide the necessary context for proper tool usage. A truly concise description would still include essential information about what an 'include' represents in this system and the scope of the update operation.

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?

For a mutation tool with no annotations and no output schema, the description is completely inadequate. It doesn't explain what an 'include' is in this domain (hotel extras? program inclusions?), what fields can be updated beyond name and description, what happens on success/failure, or any behavioral characteristics. Given the complexity of an update operation and the lack of structured metadata, this description fails to provide the necessary context for effective tool use.

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%, meaning all three parameters (id, name, description) have descriptions in the schema itself. The tool description adds no additional parameter information beyond what's already documented in the schema. According to scoring rules, when schema coverage is high (>80%), the baseline score is 3 even with no parameter information in the description.

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 un extra o incluído' is a tautology that essentially restates the tool name 'update_include' in Spanish. While it indicates the action (update) and target (extra/included), it doesn't specify what an 'include' represents in this domain or what aspects are being updated beyond the basic verb-noun pairing. It doesn't distinguish this from sibling tools like 'update_activities' or 'update_service' beyond the different resource names.

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's no mention of prerequisites, when this operation is appropriate, what happens if the include doesn't exist, or how it differs from related tools like 'create_include' or 'delete_include'. The agent receives no contextual usage information beyond the basic action implied by the name.

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