Skip to main content
Glama
lumile

LumbreTravel MCP Server

by lumile

create_agency

Create a new travel agency in LumbreTravel by providing name, description, and provider details after checking for existing agencies.

Instructions

Crear una agencia. Antes de crear una nueva agencia se debe preguntar al si quiere que primero se busque la agencia a ver si existe

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesNombre de la agencia
descriptionYesDescripción de la agencia
providerYes

Implementation Reference

  • The handler function for the 'create_agency' MCP tool. It destructures the input arguments, calls the ApiService.createAgency method, and formats the response as MCP content.
    case 'create_agency': {
      const { name, description, provider } = args
      const agency = await this.apiService.createAgency({ name, description, provider })
      return {
        content: [{ type: 'text', text: JSON.stringify(agency, null, 2) }]
      }
    }
  • The schema definition and registration of the 'create_agency' tool within the listTools() method, including name, description, and inputSchema.
    {
      name: 'create_agency',
      description: 'Crear una agencia.  Antes de crear una nueva agencia se debe preguntar al si quiere que primero se busque la agencia a ver si existe',
      inputSchema: {
        type: 'object',
        properties: {
          name: { type: 'string', description: 'Nombre de la agencia' },
          description: { type: 'string', description: 'Descripción de la agencia' },
          provider: {
            type: 'object',
            properties: {
              id: { type: 'string', description: 'ID del proveedor de la agencia.' },
              name: { type: 'string', description: 'Nombre del proveedor de la agencia' }
            }
          }
        },
        required: ['name', 'description', 'provider']
      }
    },
  • Supporting service method that makes the actual HTTP POST request to the backend API endpoint to create an agency using the provided data.
    async createAgency (data: {
      name: string
      description: string
      provider: {
        id: string
        name: string
      }
    }) {
      const headers = await this.getHeaders()
      const response = await fetch(`${API_CONFIG.baseUrl}/integrations/mcp/agency/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 the full burden of behavioral disclosure. The description mentions a prerequisite check (searching for existing agencies), which adds some context beyond basic functionality. However, it lacks details on critical behavioral traits such as whether this is a mutating operation (implied by 'create'), what permissions are required, whether the creation is idempotent, or what happens on success/failure. For a creation 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 concise and front-loaded: it states the main purpose in the first phrase ('Crear una agencia'), followed by a usage guideline. Both sentences are relevant and earn their place, with no redundant information. However, it could be slightly more structured (e.g., separating purpose from guidelines with punctuation or formatting).

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complexity (a creation tool with 3 required parameters, including a nested object, and no output schema or annotations), the description is partially complete. It covers purpose and usage guidelines well, but lacks details on behavioral aspects (e.g., mutation effects, error handling) and parameter semantics. Without annotations or output schema, the description should do more to explain what happens after creation or potential side effects.

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 67% (2 out of 3 parameters have descriptions in the schema: 'name' and 'description', but 'provider' lacks a description for its nested properties beyond IDs and names). The tool description adds no information about parameters beyond what the schema provides—it doesn't explain what 'name', 'description', or 'provider' mean in context, their formats, or constraints. With moderate schema coverage, the baseline is 3, as the description doesn't compensate for gaps.

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: 'Crear una agencia' (Create an agency). It specifies the action (create) and resource (agency), making the intent unambiguous. However, it doesn't explicitly differentiate from sibling tools like 'create_provider' or 'create_program', which are similar creation operations for different resources.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides explicit guidance on when to use this tool: 'Antes de crear una nueva agencia se debe preguntar al si quiere que primero se busque la agencia a ver si existe' (Before creating a new agency, you should ask if they want to first search for the agency to see if it exists). This indicates a prerequisite check and suggests an alternative approach (searching first), which helps the agent decide when to invoke this tool versus alternatives like 'get_agency_by_name' or 'list_agencies'.

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