Skip to main content
Glama
lumile

LumbreTravel MCP Server

by lumile

update_leader

Modify guide details like name, contact information, and language preferences in the LumbreTravel travel management system.

Instructions

Actualizar un guía

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesID del guía a actualizar
nameYesNombre del guía
descriptionYesDescripción del guía
phoneYesTeléfono del guía
languageYesIdioma del guía de acuerdo a ISO 639-1. NO intentes usar 'list_service_languages' ni 'get_service_language_by_name' para obtener el idioma del guía.
emailYesEmail del guía

Implementation Reference

  • Handler function that implements the 'update_leader' MCP tool by destructuring arguments and calling the ApiService.updateLeader method, then returning the JSON-stringified result.
    case 'update_leader': {
      const { id, name, description, phone, email, language } = args
      const leader = await this.apiService.updateLeader({ id, name, description, phone, email, language })
      return {
        content: [{ type: 'text', text: JSON.stringify(leader, null, 2) }]
      }
  • Input schema definition for the 'update_leader' tool, specifying required parameters and descriptions.
      name: 'update_leader',
      description: 'Actualizar un guía',
      inputSchema: {
        type: 'object',
        properties: {
          id: { type: 'string', description: 'ID del guía a actualizar' },
          name: { type: 'string', description: 'Nombre del guía' },
          description: { type: 'string', description: 'Descripción del guía' },
          phone: { type: 'string', description: 'Teléfono del guía' },
          language: {
            type: 'string',
            description: "Idioma del guía de acuerdo a ISO 639-1.  NO intentes usar 'list_service_languages' ni 'get_service_language_by_name' para obtener el idioma del guía."
          },
          email: { type: 'string', description: 'Email del guía' }
        },
        required: ['id', 'name', 'description', 'phone', 'email', 'language']
      }
    },
  • src/index.ts:44-47 (registration)
    Registration of the callTool request handler on the MCP server, which dispatches to ToolsHandler.callTool based on the tool name, enabling execution of 'update_leader'.
    this.server.setRequestHandler(
      CallToolRequestSchema,
      async (request) => await this.toolsHandler.callTool(request.params.name, request.params.arguments, this.server)
    )
  • src/index.ts:38-41 (registration)
    Registration of the listTools request handler on the MCP server, which returns the list including 'update_leader' tool definition.
    this.server.setRequestHandler(
      ListToolsRequestSchema,
      async () => this.toolsHandler.listTools()
    )
  • ApiService method that performs the actual HTTP PUT request to update a leader via the backend API, used by the tool handler.
    async updateLeader (data: {
      id: string
      name: string
      description: string
      phone: string
      email: string
      language: string
    }) {
      const headers = await this.getHeaders()
      const response = await fetch(`${API_CONFIG.baseUrl}/integrations/mcp/leader/update`, {
        method: 'PUT',
        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?

With no annotations provided, the description carries full burden for behavioral disclosure. 'Actualizar' implies a mutation/write operation, but the description doesn't mention required permissions, whether partial updates are supported, what happens to unspecified fields, error conditions, or side effects. The language parameter warning hints at behavioral constraints but doesn't fully compensate for the missing safety/behavioral context.

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 - a single Spanish phrase 'Actualizar un guía' - with zero wasted words. While this represents under-specification rather than ideal conciseness, it meets the technical criteria for being front-loaded and having every sentence (in this case, the only sentence) earn its place by stating the core purpose.

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 mutation tool with 6 required parameters and no annotations or output schema, the description is inadequate. It doesn't explain what 'guía' represents in this domain, doesn't provide usage context, and offers minimal behavioral transparency. The schema provides parameter documentation but the description fails to add meaningful value beyond the structured data.

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%, so the schema already documents all 6 parameters thoroughly. The description adds no parameter information beyond what's in the schema. However, the schema provides good parameter descriptions including the language parameter warning, establishing a baseline score of 3 since the schema does the heavy lifting.

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 'Actualizar un guía' is a tautology that simply restates the tool name 'update_leader' in Spanish. It doesn't specify what 'guía' refers to (likely a tour guide/leader based on context) or what fields can be updated. While it indicates a mutation operation, it lacks the specificity needed to distinguish it from sibling tools like 'create_leader' or 'reactivate_leader'.

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 related tools (create_leader, delete_leader, reactivate_leader, get_leader_by_name, list_leaders) but the description offers no context about prerequisites, when this update is appropriate, or what distinguishes it from other leader-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