Skip to main content
Glama
lumile

LumbreTravel MCP Server

by lumile

create_service

Add new travel services to the LumbreTravel platform by specifying service name, description, and provider details for program management.

Instructions

Crear un servicio

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesNombre del servicio
descriptionYesDescripción del servicio
providerYes

Implementation Reference

  • Handler implementation for the 'create_service' tool. It destructures the input arguments (name, description, provider), calls ApiService.createService, and returns the created service as JSON text.
    case 'create_service': {
      const { name, description, provider } = args
      const service = await this.apiService.createService({ name, description, provider })
      return {
        content: [{ type: 'text', text: JSON.stringify(service, null, 2) }]
      }
    }
  • Input schema and metadata definition for the 'create_service' tool, returned by listTools().
      name: 'create_service',
      description: 'Crear un servicio',
      inputSchema: {
        type: 'object',
        properties: {
          name: { type: 'string', description: 'Nombre del servicio' },
          description: { type: 'string', description: 'Descripción del servicio' },
          provider: {
            type: 'object',
            properties: {
              id: { type: 'string', description: 'ID del proveedor' },
              name: { type: 'string', description: 'Nombre del proveedor' }
            }
          }
        },
        required: ['name', 'description', 'provider']
      }
    },
  • ApiService.createService method that performs the HTTP POST request to the backend API endpoint to create a new service.
    async createService (data: {
      name: string
      description: string
      provider: {
        id: string
        name: string
      }
    }) {
      const headers = await this.getHeaders()
      const response = await fetch(`${API_CONFIG.baseUrl}/integrations/mcp/service/create`, {
        method: 'POST',
        headers: { ...headers, 'Content-Type': 'application/json' },
        body: JSON.stringify(data)
      })
      return await this.handleResponse<any>(response)
  • src/index.ts:38-47 (registration)
    MCP server request handlers for listing tools (which includes 'create_service') and calling tools (dispatches to ToolsHandler based on name).
    this.server.setRequestHandler(
      ListToolsRequestSchema,
      async () => this.toolsHandler.listTools()
    )
    
    // Configure handlers for tools
    this.server.setRequestHandler(
      CallToolRequestSchema,
      async (request) => await this.toolsHandler.callTool(request.params.name, request.params.arguments, this.server)
    )
  • Import of ApiService used by the tools handler.
    import { ApiService } from '../services/api.service.js'
    import { formatDate } from '../utils/date.utils.js'
    import { type Server } from '@modelcontextprotocol/sdk/server/index.js'
    
    export class ToolsHandler {
      private readonly apiService: ApiService
    
      constructor () {
        this.apiService = new ApiService()
      }
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. 'Crear un servicio' only indicates this is a creation operation but reveals nothing about permissions required, whether this is a mutating operation (implied but not stated), what happens on success/failure, rate limits, or any other behavioral characteristics. For a creation tool with zero annotation coverage, this is completely inadequate.

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 maximally concise - a single Spanish phrase 'Crear un servicio'. While this represents severe under-specification, from a pure conciseness perspective, it's front-loaded with zero wasted words. Every word (both of them) directly states the tool's action.

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 creation tool with 3 required parameters (including a nested object), no annotations, no output schema, and 67% schema coverage, the description is completely inadequate. It provides no context about what a service is in this domain, what happens after creation, error conditions, or how this fits with the many sibling tools. The description fails to compensate for the lack of structured metadata.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 67% (2 of 3 parameters have descriptions in the schema), but the description adds zero information about parameters. It doesn't explain what a 'service' consists of, what the provider object represents, or provide any context beyond what's minimally documented in the schema. With 3 required parameters including a nested object, the description should add meaningful context about parameter relationships and semantics.

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 servicio' is a tautology that essentially restates the tool name 'create_service' in Spanish. It doesn't specify what kind of service is being created or what domain this operates in, nor does it differentiate from sibling tools like 'create_agency', 'create_hotel', or 'create_provider' which appear to be similar creation operations in the same system.

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 absolutely no guidance about when to use this tool versus alternatives. With many sibling tools including other 'create_' operations and various 'get_', 'list_', 'update_', and 'delete_' tools, there's no indication of when this specific service creation tool is appropriate versus creating other entities or using related operations.

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