Skip to main content
Glama

volkern_create_cita

Schedule appointments in Volkern CRM by specifying lead ID, date/time, type, and details to organize client meetings and services.

Instructions

Create a new appointment. Check availability first with volkern_check_disponibilidad.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
leadIdYesID of the lead for this appointment
fechaHoraYesAppointment date/time in ISO 8601 UTC (e.g., 2026-02-10T10:00:00Z)
tipoNoAppointment type (default: reunion)
tituloNoAppointment title
descripcionNoAppointment description or notes
duracionNoDuration in minutes (default: 60)
servicioIdNoService ID (required if tipo is 'servicio')

Implementation Reference

  • The handler for volkern_create_cita tool - a switch case that calls volkernRequest to POST appointment data to the /citas endpoint
    case "volkern_create_cita":
      return volkernRequest("/citas", "POST", args);
  • Tool schema definition for volkern_create_cita - defines the tool name, description, and inputSchema with properties for leadId, fechaHora, tipo, titulo, descripcion, duracion, and servicioId
    {
      name: "volkern_create_cita",
      description: "Create a new appointment. Check availability first with volkern_check_disponibilidad.",
      inputSchema: {
        type: "object",
        properties: {
          leadId: { type: "string", description: "ID of the lead for this appointment" },
          fechaHora: { type: "string", description: "Appointment date/time in ISO 8601 UTC (e.g., 2026-02-10T10:00:00Z)" },
          tipo: {
            type: "string",
            enum: ["reunion", "servicio", "llamada", "otro"],
            description: "Appointment type (default: reunion)"
          },
          titulo: { type: "string", description: "Appointment title" },
          descripcion: { type: "string", description: "Appointment description or notes" },
          duracion: { type: "number", description: "Duration in minutes (default: 60)" },
          servicioId: { type: "string", description: "Service ID (required if tipo is 'servicio')" }
        },
        required: ["leadId", "fechaHora"]
      }
    },
  • The volkernRequest helper function used by the handler - makes HTTP requests to the Volkern API with authentication headers and handles responses/errors
    async function volkernRequest(
      endpoint: string,
      method: string = "GET",
      body?: Record<string, unknown>
    ): Promise<unknown> {
      const url = `${VOLKERN_API_URL}${endpoint}`;
      
      const options: RequestInit = {
        method,
        headers: {
          "Authorization": `Bearer ${VOLKERN_API_KEY}`,
          "Content-Type": "application/json",
        },
      };
    
      if (body && method !== "GET") {
        options.body = JSON.stringify(body);
      }
    
      const response = await fetch(url, options);
      
      if (!response.ok) {
        const errorData = await response.json().catch(() => ({}));
        throw new Error(
          `Volkern API Error (${response.status}): ${JSON.stringify(errorData)}`
        );
      }
    
      return response.json();
    }
  • The complete handleToolCall function that contains the switch statement routing tool calls to their respective handlers, including volkern_create_cita
    async function handleToolCall(
      name: string,
      args: Record<string, unknown>
    ): Promise<unknown> {
      switch (name) {
        // LEADS
        case "volkern_list_leads": {
          const params = new URLSearchParams();
          if (args.estado) params.append("estado", String(args.estado));
          if (args.canal) params.append("canal", String(args.canal));
          if (args.search) params.append("search", String(args.search));
          if (args.page) params.append("page", String(args.page));
          if (args.limit) params.append("limit", String(args.limit));
          return volkernRequest(`/leads?${params.toString()}`);
        }
        case "volkern_get_lead":
          return volkernRequest(`/leads/${args.leadId}`);
        case "volkern_create_lead":
          return volkernRequest("/leads", "POST", args);
        case "volkern_update_lead": {
          const { leadId, ...data } = args;
          return volkernRequest(`/leads/${leadId}`, "PATCH", data);
        }
    
        // APPOINTMENTS
        case "volkern_check_disponibilidad": {
          const params = new URLSearchParams();
          params.append("fecha", String(args.fecha));
          if (args.duracion) params.append("duracion", String(args.duracion));
          return volkernRequest(`/citas/disponibilidad?${params.toString()}`);
        }
        case "volkern_list_citas": {
          const params = new URLSearchParams();
          if (args.estado) params.append("estado", String(args.estado));
          if (args.tipo) params.append("tipo", String(args.tipo));
          if (args.fecha) params.append("fecha", String(args.fecha));
          if (args.fechaInicio) params.append("fechaInicio", String(args.fechaInicio));
          if (args.fechaFin) params.append("fechaFin", String(args.fechaFin));
          return volkernRequest(`/citas?${params.toString()}`);
        }
        case "volkern_create_cita":
          return volkernRequest("/citas", "POST", args);
  • src/index.ts:961-986 (registration)
    The CallToolRequestSchema handler registration that receives tool call requests and delegates to handleToolCall function
    server.setRequestHandler(CallToolRequestSchema, async (request) => {
      const { name, arguments: args } = request.params;
    
      try {
        const result = await handleToolCall(name, args as Record<string, unknown>);
        return {
          content: [
            {
              type: "text",
              text: JSON.stringify(result, null, 2),
            },
          ],
        };
      } catch (error) {
        const errorMessage = error instanceof Error ? error.message : String(error);
        return {
          content: [
            {
              type: "text",
              text: `Error: ${errorMessage}`,
            },
          ],
          isError: true,
        };
      }
    });
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. While 'Create' implies a write/mutation operation, the description doesn't mention permissions required, whether the appointment is confirmed immediately, error conditions (e.g., if the time slot is taken despite checking), or what happens on success/failure. For a creation tool with zero annotation coverage, this leaves significant gaps in understanding its behavior.

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 two sentences with zero waste: the first states the core purpose, and the second provides critical usage guidance. It's front-loaded with the main action and appropriately sized for the tool's complexity.

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 tool's moderate complexity (7 parameters, creation operation) and lack of annotations or output schema, the description is minimally adequate. It covers purpose and a key prerequisite but misses behavioral details like what the tool returns or error handling. The usage guideline is helpful, but overall completeness is limited for a mutation tool without structured support.

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?

The schema description coverage is 100%, meaning all parameters are documented in the input schema itself. The description adds no additional parameter information beyond what's in the schema (e.g., it doesn't explain relationships like 'servicioId' being required only for 'tipo=servicio', though the schema covers this). With high schema coverage, the baseline is 3 even without param details in the description.

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 verb ('Create') and resource ('new appointment'), making the purpose immediately understandable. It distinguishes this from sibling tools like 'volkern_list_citas' (list) and 'volkern_update_cita' (update), though it doesn't explicitly differentiate from other creation tools like 'volkern_create_contact' or 'volkern_create_lead' 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 Guidelines5/5

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

The description provides explicit usage guidance by stating 'Check availability first with volkern_check_disponibilidad.' This directly tells the agent when to use this tool (after checking availability) and names the specific alternative tool to use beforehand, which is ideal for preventing errors.

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/DeXpertmx/mcp-volkern'

If you have feedback or need assistance with the MCP directory API, please join our Discord server