Skip to main content
Glama

octadezx_schedule_appointment

Book an appointment request and check Google Calendar staff availability in OctaDezx Cloud using customer name, phone, and service details.

Instructions

Create an appointment booking request and check Google Calendar staff busy-time availability in your OctaDezx Cloud workspace. Use after confirming service type, customer name, and callback phone number. Requires OCTADEZX_API_KEY; returns a structured 'requires_api_key' error payload when no API key is configured.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "customerName": "<customerName>",
      "phone": "<phone>",
      "service": "<service>"
    },
    "name": "octadezx_schedule_appointment"
  }
}

Input Schema

NameRequiredDescriptionDefault
phoneYesCustomer contact phone number for SMS/WhatsApp/voice booking confirmation.
serviceYesName of the requested service, consultation, or salon/clinic treatment.
datetimeNoOptional preferred appointment start date and time in ISO 8601 format (for example, '2026-11-18T14:30:00Z').
customerNameYesFull name of the customer requesting the appointment.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changedv1.2.1
    • addedInput schema / additionalProperties
      Added value: +false
    • changedInput schema / properties / customerName / description
      Previous value: -"Customer full name"New value: +"Full name of the customer requesting the appointment."
    • addedInput schema / properties / customerName / minLength
      Added value: +1
    • changedInput schema / properties / datetime / description
      Previous value: -"Preferred ISO datetime"New value: +"Optional preferred appointment start date and time in ISO 8601 format (for example, '2026-11-18T14:30:00Z')."
    • changedInput schema / properties / phone / description
      Previous value: -"Contact phone number"New value: +"Customer contact phone number for SMS/WhatsApp/voice booking confirmation."
    • addedInput schema / properties / phone / minLength
      Added value: +5
    • changedInput schema / properties / service / description
      Previous value: -"Requested service or treatment"New value: +"Name of the requested service, consultation, or salon/clinic treatment."
    • addedInput schema / properties / service / minLength
      Added value: +1
  2. First observedv1.0.0

TDQS

A3.8/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Beyond the annotations (which already declare non-read-only, open-world, non-idempotent, non-destructive), the description discloses the OCTADEZX_API_KEY requirement and the specific 'requires_api_key' error payload returned when it is absent. It also reveals the external Google Calendar dependency, corroborating openWorldHint, though it does not warn that repeated calls can create duplicate bookings despite idempotentHint=false.

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

Conciseness4/5

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

Two sentences, front-loaded with the core action and followed by the precondition and auth note; every clause carries information. Minor trimming is possible, but there is no filler or repetition.

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?

With no output schema, the description should explain what a successful call yields, yet it only describes the failure path ('requires_api_key'). An agent cannot tell whether success returns a confirmed slot, a pending request ID, or busy-time intervals, which matters given the tool mixes booking creation with availability checking.

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 phone, service, datetime, and customerName are already documented with examples and format hints. The description only mentions which fields should be confirmed beforehand and adds no new meaning (e.g., whether datetime is required to check availability), so the baseline of 3 applies.

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 names two specific actions with concrete resources: creating an appointment booking request and checking Google Calendar staff busy-time availability. No sibling in the list touches appointment scheduling, so the agent can identify this tool's role immediately from verb+resource alone.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

'Use after confirming service type, customer name, and callback phone number' gives a sequencing precondition for invocation. However, it only restates the required parameters and offers no when-not guidance or comparison to alternatives such as trigger_voice_call, so the usage context is implied rather than complete.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.