Skip to main content
Glama
lumile

LumbreTravel MCP Server

by lumile

create_include

Add optional extras or inclusions to travel programs by defining names and descriptions for enhanced booking customization.

Instructions

Crear un extra o incluído.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesNombre
descriptionYesDescripción

Implementation Reference

  • Handler implementation for the 'create_include' tool. Extracts name and description from arguments, calls ApiService.createInclude, and returns the JSON response.
    case 'create_include': {
      const { name, description } = args
      const include = await this.apiService.createInclude({ name, description })
      return {
        content: [{ type: 'text', text: JSON.stringify(include, null, 2) }]
      }
    }
  • Schema definition for the 'create_include' tool, including input schema requiring 'name' and 'description' strings.
    name: 'create_include',
    description: 'Crear un extra o incluído.',
    inputSchema: {
      type: 'object',
      properties: {
        name: { type: 'string', description: 'Nombre' },
        description: { type: 'string', description: 'Descripción' }
      },
      required: ['name', 'description']
    }
  • The 'create_include' tool is registered in the listTools() method's tools array, advertised to MCP clients.
    {
      name: 'create_include',
      description: 'Crear un extra o incluído.',
      inputSchema: {
        type: 'object',
        properties: {
          name: { type: 'string', description: 'Nombre' },
          description: { type: 'string', description: 'Descripción' }
        },
        required: ['name', 'description']
      }
    },
  • Helper method in ApiService that performs the HTTP POST request to create an include via the LumbreTravel API.
    async createInclude (data: {
      name: string
      description: string
    }) {
      const headers = await this.getHeaders()
      const response = await fetch(`${API_CONFIG.baseUrl}/integrations/mcp/include/create`, {
        method: 'POST',
        headers: { ...headers, 'Content-Type': 'application/json' },
        body: JSON.stringify(data)
      })
      return await this.handleResponse<any>(response)
    }
Behavior2/5

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

No annotations are provided, so the description carries full burden. 'Crear' implies a write/mutation operation, but the description doesn't disclose behavioral traits like required permissions, whether creation is idempotent, what happens on conflicts, or the response format. It lacks essential context for a creation tool.

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 a single, concise sentence in Spanish. However, it's under-specified rather than efficiently informative—it uses minimal words but fails to convey useful information beyond the tool name.

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 creation tool with no annotations and no output schema, the description is inadequate. It doesn't explain what an 'include' is in this domain, what happens after creation, or any prerequisites. Given the complexity implied by sibling tools (e.g., includes vs. services), more context is needed for effective 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%, with both parameters (name, description) documented in the schema. The description adds no meaning beyond the schema—it doesn't explain what 'name' or 'description' represent for an 'include', their constraints, or examples. Baseline 3 is appropriate since the schema does the heavy lifting.

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 'Crear un extra o incluído' (Create an extra or included) restates the tool name 'create_include' in Spanish, making it tautological. It doesn't specify what resource is being created beyond the vague 'extra o incluído', nor does it distinguish this from sibling tools like 'create_service' or 'create_program'.

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?

No guidance is provided on when to use this tool versus alternatives. With many sibling tools for creating different entities (e.g., create_agency, create_hotel, create_service), the description offers no context on what an 'include' represents or when it's appropriate to create one.

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