Skip to main content
Glama
lumile

LumbreTravel MCP Server

by lumile

create_provider

Add new travel service providers to the LumbreTravel system by entering their name, description, contact details, and other required information.

Instructions

Crear un proveedor.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesNombre del proveedor
descriptionYesDescripción del proveedor
emailNoEmail del proveedor, si no tiene email se puede dejar en blanco
phoneNoTeléfono del proveedor, si no tiene teléfono se puede dejar en blanco

Implementation Reference

  • Handler function for the 'create_provider' tool within the callTool switch statement. Extracts arguments, calls ApiService.createProvider, and returns the JSON response.
    case 'create_provider': {
      const { name, description, phone, email } = args
      const provider = await this.apiService.createProvider({ name, description, phone, email })
      return {
        content: [{ type: 'text', text: JSON.stringify(provider, null, 2) }]
      }
    }
  • Tool schema definition including name, description, and inputSchema for 'create_provider' in the listTools method.
      name: 'create_provider',
      description: 'Crear un proveedor.',
      inputSchema: {
        type: 'object',
        properties: {
          name: { type: 'string', description: 'Nombre del proveedor' },
          description: { type: 'string', description: 'Descripción del proveedor' },
          email: { type: 'string', description: 'Email del proveedor, si no tiene email se puede dejar en blanco' },
          phone: { type: 'string', description: 'Teléfono del proveedor, si no tiene teléfono se puede dejar en blanco' }
        },
        required: ['name', 'description']
      }
    },
  • ApiService.createProvider method that performs the HTTP POST request to the backend API to create a provider.
    async createProvider (data: {
      name: string
      description: string
      phone: string
      email: string
    }) {
      const headers = await this.getHeaders()
      const response = await fetch(`${API_CONFIG.baseUrl}/integrations/mcp/provider/create`, {
        method: 'POST',
        headers: { ...headers, 'Content-Type': 'application/json' },
        body: JSON.stringify(data)
      })
      return await this.handleResponse<any>(response)
    }
  • src/index.ts:44-48 (registration)
    MCP server registration of the callTool handler, which dispatches to ToolsHandler.callTool based on tool name.
      this.server.setRequestHandler(
        CallToolRequestSchema,
        async (request) => await this.toolsHandler.callTool(request.params.name, request.params.arguments, this.server)
      )
    }
  • src/index.ts:38-41 (registration)
    MCP server registration of the listTools handler, which provides the tool list including 'create_provider'.
    this.server.setRequestHandler(
      ListToolsRequestSchema,
      async () => this.toolsHandler.listTools()
    )
Behavior1/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 only states 'Crear un proveedor' which implies a write/mutation operation but reveals nothing about permissions required, whether creation is idempotent, what happens on duplicate names, error conditions, or response format. For a mutation tool with zero annotation coverage, this is critically insufficient.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely concise at just three words ('Crear un proveedor'). While this represents under-specification rather than ideal conciseness, according to the scoring framework, conciseness evaluates whether the description is appropriately sized and front-loaded. This description wastes no words and gets straight to the point, earning full marks on this dimension despite its inadequacy elsewhere.

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

Completeness1/5

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

Given this is a mutation tool (create operation) with no annotations and no output schema, the description is completely inadequate. It doesn't explain what a provider is, when to create one, what permissions are needed, what the response contains, or how it differs from other creation tools. The description fails to provide the necessary context for an agent to use this tool 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?

Schema description coverage is 100%, meaning all parameters (name, description, email, phone) are documented in the input schema with descriptions. The tool description adds no additional parameter information beyond what's already in the schema. According to the scoring rules, when schema coverage is high (>80%), the baseline score is 3 even with no param info in the description.

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

Purpose2/5

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

The description 'Crear un proveedor' (Create a provider) is a tautology that essentially restates the tool name 'create_provider' in Spanish. While it indicates the action (create) and resource (provider), it doesn't specify what a 'provider' represents in this context or differentiate it from similar creation tools like create_agency, create_hotel, etc. The purpose is stated 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 Guidelines1/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. There are multiple sibling creation tools (e.g., create_agency, create_hotel, create_program) with no indication of what distinguishes a 'provider' from these other entities. No prerequisites, context, or exclusions are mentioned.

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