Skip to main content
Glama
lumile

LumbreTravel MCP Server

by lumile

get_leader_by_name

Search for travel guides by name to find specific leaders for your travel programs and activities using the LumbreTravel API.

Instructions

Buscar guías por su nombre.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesNombre del guía

Implementation Reference

  • Handler logic for the 'get_leader_by_name' tool: extracts 'name' from args, calls apiService.getLeaderByName(name), and returns the result as JSON text content.
    case 'get_leader_by_name': {
      const { name } = args as { name: string }
      const leader = await this.apiService.getLeaderByName(name)
      return {
        content: [{ type: 'text', text: JSON.stringify(leader, null, 2) }]
      }
    }
  • Input schema definition for the 'get_leader_by_name' tool, specifying a required 'name' string parameter.
    {
      name: 'get_leader_by_name',
      description: 'Buscar guías por su nombre.',
      inputSchema: { type: 'object', properties: { name: { type: 'string', description: 'Nombre del guía' } }, required: ['name'] }
    },
  • The tool is registered in the listTools() method which returns the list of available tools including 'get_leader_by_name'.
        ]
      }
    }
  • Helper method in ApiService that performs a POST request to the backend API endpoint '/integrations/mcp/leader/get_leaders_by_name' with the leader name to retrieve leader data.
    async getLeaderByName (name: string) {
      const headers = await this.getHeaders()
      const response = await fetch(`${API_CONFIG.baseUrl}/integrations/mcp/leader/get_leaders_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 of behavioral disclosure. It only states the search action without detailing what 'buscar' entails—e.g., whether it's a read-only operation, if it returns exact or partial matches, error handling, or authentication needs. For a tool with no annotations, this leaves critical behavioral traits unspecified.

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 ('Buscar guías por su nombre.') that is front-loaded and wastes no words. However, it's slightly under-specified given the lack of annotations and sibling context, which affects completeness more than conciseness.

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 complexity (a search tool with no annotations and no output schema), the description is incomplete. It doesn't explain what 'guías' are, how results are returned, or any behavioral nuances. With no output schema, the description should ideally hint at return values or search behavior, but it fails to do so, leaving gaps for the agent.

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 'name' parameter documented as 'Nombre del guía'. The description adds no additional meaning beyond this, as it merely restates the parameter's purpose. With high schema coverage, the baseline score of 3 is appropriate, as the description doesn't compensate but also doesn't detract.

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 guías por su nombre' (Search guides by their name) states a clear verb ('buscar') and resource ('guías'), but it's vague about what 'guías' refers to (likely leaders/guides based on tool name) and doesn't differentiate from sibling tools like 'get_agency_by_name' or 'get_hotel_by_name' that follow the same pattern. It's functional but lacks specificity.

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 guidance is provided on when to use this tool versus alternatives. There's no mention of prerequisites, when-not-to-use scenarios, or comparisons to sibling tools like 'list_leaders' (which might retrieve all leaders without filtering). The description implies usage for searching by name but offers no contextual boundaries.

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