Skip to main content
Glama

volkern_check_disponibilidad

Check available time slots for a specific date to schedule appointments. Use this tool before booking to verify availability based on duration requirements.

Instructions

Check available time slots for a specific date. Always call this before booking.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fechaYesDate in YYYY-MM-DD format
duracionNoDuration in minutes (default: 60)

Implementation Reference

  • Handler for volkern_check_disponibilidad tool - constructs query parameters (fecha and optional duracion) and calls the Volkern API endpoint /citas/disponibilidad
    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()}`);
    }
  • Tool schema definition for volkern_check_disponibilidad - defines input parameters: fecha (required date string in YYYY-MM-DD format) and duracion (optional duration in minutes)
    {
      name: "volkern_check_disponibilidad",
      description: "Check available time slots for a specific date. Always call this before booking.",
      inputSchema: {
        type: "object",
        properties: {
          fecha: { type: "string", description: "Date in YYYY-MM-DD format" },
          duracion: { type: "number", description: "Duration in minutes (default: 60)" }
        },
        required: ["fecha"]
      }
    },
  • Helper function that makes HTTP requests to the Volkern API - handles authentication with Bearer token, JSON serialization, and error handling
    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();
    }
  • src/index.ts:961-986 (registration)
    MCP server request handler registration for CallToolRequestSchema - dispatches tool calls to handleToolCall function and formats responses
    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,
        };
      }
    });
Behavior3/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. It states the tool checks availability, which implies a read-only operation, but doesn't disclose behavioral details like whether it requires authentication, how it handles errors, or if it has rate limits. The description adds basic context but lacks depth for a tool with no annotation coverage.

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, front-loaded with the core purpose and followed by usage guidance. Every word earns its place with zero waste, making it highly efficient and easy to parse.

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

Completeness4/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 (availability checking), no annotations, and no output schema, the description is reasonably complete. It covers purpose and usage well but lacks details on return values (e.g., format of time slots) and behavioral constraints, which would be needed for full completeness.

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 both parameters ('fecha' as date in YYYY-MM-DD format, 'duracion' as duration in minutes with default 60). The description doesn't add meaning beyond this, such as explaining what 'available time slots' represent or how duration affects results. Baseline 3 is appropriate when schema does the heavy lifting.

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

Purpose5/5

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

The description clearly states the specific action ('Check available time slots') and resource ('for a specific date'), distinguishing it from sibling tools like 'volkern_create_cita' (booking) and 'volkern_list_citas' (listing appointments). It uses a precise verb ('Check') rather than a generic term.

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 explicitly provides when-to-use guidance: 'Always call this before booking.' This directly addresses the relationship with booking tools (e.g., 'volkern_create_cita'), making it clear this is a prerequisite step.

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