Skip to main content
Glama
lumile

LumbreTravel MCP Server

by lumile

get_includes_by_name

Search for travel extras or inclusions by name to find specific add-ons for travel programs and activities.

Instructions

Buscar extras o incluídos por su nombre

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesNombre del include

Implementation Reference

  • Registration of the 'get_includes_by_name' tool in listTools(), including name, description, and input schema.
    {
      name: 'get_includes_by_name',
      description: 'Buscar extras o incluídos por su nombre',
      inputSchema: { type: 'object', properties: { name: { type: 'string', description: 'Nombre del include' } }, required: ['name'] }
    },
  • Input schema for get_includes_by_name tool: object with required 'name' string.
    inputSchema: { type: 'object', properties: { name: { type: 'string', description: 'Nombre del include' } }, required: ['name'] }
  • Handler implementation in callTool switch: calls apiService.getIncludesByName and returns JSON stringified response.
    case 'get_includes_by_name': {
      const { name } = args as { name: string }
      const includes = await this.apiService.getIncludesByName(name)
      return {
        content: [{ type: 'text', text: JSON.stringify(includes, null, 2) }]
      }
    }
  • Supporting ApiService method that fetches includes by name from backend API endpoint.
    async getIncludesByName (name: string) {
      const headers = await this.getHeaders()
      const response = await fetch(`${API_CONFIG.baseUrl}/integrations/mcp/include/get_includes_by_name`, {
        method: 'POST',
        headers: { ...headers, 'Content-Type': 'application/json' },
        body: JSON.stringify({ name })
      })
      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 the full burden. It states the tool searches by name, but doesn't disclose behavioral traits such as whether it's read-only, if it returns partial matches, error handling, or performance characteristics. This is inadequate for a tool with no annotation coverage.

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 function. It's front-loaded with the core action and resource, with no wasted words, though the ambiguity in terminology slightly reduces clarity.

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 no annotations and no output schema, the description is incomplete. It doesn't explain what 'extras o incluídos' are, the return format, or any behavioral context. For a search tool in a domain with many siblings, more detail is needed to guide the agent effectively.

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?

The input schema has 100% description coverage, with the parameter 'name' documented as 'Nombre del include'. The description adds no additional meaning beyond this, as it only repeats the search-by-name concept. Baseline score of 3 is appropriate since the schema fully describes the parameter.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Buscar extras o incluídos por su nombre' specifies the action (buscar/search) and resource (extras o incluídos), but it's vague about what 'extras o incluídos' refers to in this domain. It distinguishes from siblings like 'list_includes' by indicating a name-based search rather than listing all, but the terminology is ambiguous.

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?

No explicit guidance on when to use this tool versus alternatives like 'list_includes' or other 'get_by_name' siblings (e.g., 'get_agency_by_name'). The description implies usage for searching by name, but it doesn't specify contexts, prerequisites, or exclusions, leaving the agent to infer from the name alone.

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