Skip to main content
Glama
lumile

LumbreTravel MCP Server

by lumile

list_includes

Retrieve available extras and inclusions to associate with travel activities in trip programs. This tool helps travel planners add optional services to activities.

Instructions

Obtiene todos los incluye o extras disponibles para asociar a una actividad en un programa de viajes

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • MCP tool handler implementation for 'list_includes': calls ApiService.getIncludes() and formats response as MCP content.
    case 'list_includes': {
      const includes = await this.apiService.getIncludes()
      return {
        content: [{
          type: 'text',
          text: JSON.stringify(includes, null, 2)
        }]
      }
    }
  • Core API call to retrieve the list of includes/extras from the backend API endpoint.
    async getIncludes () {
      const headers = await this.getHeaders()
      const response = await fetch(`${API_CONFIG.baseUrl}/integrations/mcp/includes`, {
        method: 'GET',
        headers
      })
      return await this.handleResponse<any[]>(response)
    }
  • Tool schema definition including name, description, and empty input schema (no parameters required).
      name: 'list_includes',
      description: 'Obtiene todos los incluye o extras disponibles para asociar a una actividad en un programa de viajes',
      inputSchema: {
        type: 'object',
        properties: {}
      }
    },
  • src/index.ts:44-47 (registration)
    Registers the CallToolRequestHandler which dispatches to tools.handler.ts.callTool based on tool name, enabling execution of list_includes.
    this.server.setRequestHandler(
      CallToolRequestSchema,
      async (request) => await this.toolsHandler.callTool(request.params.name, request.params.arguments, this.server)
    )
  • src/index.ts:38-41 (registration)
    Registers the ListToolsRequestHandler which returns the list of available tools including 'list_includes'.
    this.server.setRequestHandler(
      ListToolsRequestSchema,
      async () => this.toolsHandler.listTools()
    )
Behavior2/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. It indicates a read operation ('Obtiene') but does not disclose behavioral traits such as whether it requires authentication, has rate limits, returns paginated results, or what format the data is in. The description is minimal and misses key operational details needed for safe and effective use.

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, efficient sentence in Spanish that directly states the tool's purpose without unnecessary words. It is front-loaded with the key action and resource. However, it could be slightly more structured by explicitly mentioning the lack of parameters or output details.

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?

Given the tool has no parameters and no output schema, the description is incomplete. It does not explain what the return values look like (e.g., list format, data structure), any dependencies, or error conditions. For a retrieval tool in a system with many siblings, more context is needed to ensure proper use without relying on trial and error.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description does not add parameter information, which is appropriate here. A baseline of 4 is applied as it correctly avoids redundancy, though it could briefly note the lack of parameters for clarity.

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 ('Obtiene' - Gets/Retrieves) and the resource ('todos los incluye o extras disponibles' - all available includes or extras), specifying their purpose ('para asociar a una actividad en un programa de viajes' - to associate with an activity in a travel program). It distinguishes from siblings like 'get_includes_by_name' by indicating it retrieves all available includes rather than filtered ones. However, it could be more specific about what 'includes or extras' entail.

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 when needing to associate includes/extras with activities in travel programs, suggesting it's for retrieval purposes. However, it lacks explicit guidance on when to use this tool versus alternatives like 'get_includes_by_name' (which filters by name) or 'create_include' (for creation), and does not mention any prerequisites or 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