Skip to main content
Glama
lumile

LumbreTravel MCP Server

by lumile

get_agency_by_name

Retrieve a travel agency's details by entering its name. Use this tool to find specific agency information within the LumbreTravel system.

Instructions

Obtener una agencia por nombre, retorna la agencia encontrada.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesNombre de la agencia

Implementation Reference

  • MCP tool execution handler: extracts 'name' argument, calls apiService.getAgencyByName, returns JSON-formatted agency data.
    case 'get_agency_by_name': {
      const { name } = args as { name: string }
      const agency = await this.apiService.getAgencyByName(name)
      return {
        content: [{ type: 'text', text: JSON.stringify(agency, null, 2) }]
      }
    }
  • Tool schema definition in listTools(): specifies name, description, and input schema requiring 'name' string.
      name: 'get_agency_by_name',
      description: 'Obtener una agencia por nombre, retorna la agencia encontrada.',
      inputSchema: {
        type: 'object',
        properties: { name: { type: 'string', description: 'Nombre de la agencia' } },
        required: ['name']
      }
    },
  • API service helper: performs POST request to backend endpoint /agency/get_agencies_by_name with {name} body.
    async getAgencyByName (name: string) {
      const headers = await this.getHeaders()
      const response = await fetch(`${API_CONFIG.baseUrl}/integrations/mcp/agency/get_agencies_by_name`, {
        method: 'POST',
        headers: { ...headers, 'Content-Type': 'application/json' },
        body: JSON.stringify({ name })
      })
      return await this.handleResponse<any>(response)
    }
  • src/index.ts:44-47 (registration)
    MCP server registration of tool handlers: CallToolRequestSchema routes to toolsHandler.callTool, ListToolsRequestSchema to listTools.
    this.server.setRequestHandler(
      CallToolRequestSchema,
      async (request) => await this.toolsHandler.callTool(request.params.name, request.params.arguments, this.server)
    )
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states the tool returns the found agency ('retorna la agencia encontrada'), which is basic output information. However, it doesn't describe error handling (e.g., what happens if no agency matches the name), authentication requirements, rate limits, or whether it's a read-only operation. For a lookup tool with zero annotation coverage, this is insufficient.

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 states the action and outcome. It's appropriately sized for a simple lookup tool with one parameter. However, it could be slightly more structured by separating purpose from behavior.

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 lookup tool with no annotations and no output schema, the description is incomplete. It mentions the return value but doesn't describe the response format, error cases, or behavioral constraints. Given the server context with many sibling tools, more guidance on when to use this versus alternatives would be valuable.

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 one parameter 'name' documented as 'Nombre de la agencia'. The description doesn't add any additional parameter semantics beyond what the schema provides (e.g., format expectations, case sensitivity, examples). Since the schema does the heavy lifting, the baseline score of 3 is appropriate.

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 tool's purpose: 'Obtener una agencia por nombre' (Get an agency by name) with the verb 'obtener' and resource 'agencia'. It distinguishes from sibling 'list_agencies' by specifying retrieval by name rather than listing all. However, it doesn't explicitly differentiate from other 'get_by_name' tools like 'get_hotel_by_name' beyond the resource type.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention sibling tools like 'list_agencies' for broader queries or 'create_agency' for adding new agencies. There's no context about prerequisites, error conditions, or typical use cases.

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