Skip to main content
Glama
andymillar84-cyber

mcp-cliniko

update_appointment

Modify an existing appointment's start time, notes, or patient ID by providing the appointment ID.

Instructions

Update an existing appointment

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
appointment_idYesAppointment ID
starts_atNoNew start time (ISO 8601)
notesNoUpdated notes
patient_idNoNew patient ID

Implementation Reference

  • The async handler function for the 'update_appointment' tool. It destructures appointment_id from the input, passes remaining fields to client.updateAppointment(), and returns the updated appointment as JSON.
    }, async ({ appointment_id, ...updateData }: any) => {
      try {
        const appointment = await client.updateAppointment(appointment_id, updateData);
        return {
          content: [{
            type: 'text',
            text: JSON.stringify(appointment, null, 2)
          }]
        };
      } catch (error) {
        throw new Error(`Failed to update appointment: ${error instanceof Error ? error.message : 'Unknown error'}`);
      }
    });
  • The tool registration and input schema for 'update_appointment'. The schema requires 'appointment_id' and allows optional fields: 'starts_at', 'notes', and 'patient_id'.
    // Update appointment
    server.tool('update_appointment', {
      description: 'Update an existing appointment',
      inputSchema: {
        type: 'object',
        properties: {
          appointment_id: { type: 'number', description: 'Appointment ID' },
          starts_at: { type: 'string', description: 'New start time (ISO 8601)' },
          notes: { type: 'string', description: 'Updated notes' },
          patient_id: { type: 'number', description: 'New patient ID' }
        },
        required: ['appointment_id']
  • src/index.ts:58-59 (registration)
    The tool is registered via registerAppointmentTools(toolRegistry, clinikoClient) called in the main index.ts entry point.
    registerPatientTools(toolRegistry, clinikoClient);
    registerAppointmentTools(toolRegistry, clinikoClient);
  • The ClinikoClient.updateAppointment() method that sends a PUT request to /appointments/{id} with the partial appointment data to update.
    async updateAppointment(id: number, appointment: Partial<Appointment>): Promise<Appointment> {
      return this.request<Appointment>(`/appointments/${id}`, {
        method: 'PUT',
        body: JSON.stringify(appointment),
      });
    }
Behavior2/5

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

With no annotations, the description should disclose update behavior (e.g., partial vs full update, validation, return value). It only says 'update', leaving important behavioral traits unspecified.

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 a single, concise sentence with no unnecessary words. It is appropriately sized and front-loaded.

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?

Given the tool has 4 parameters (1 required) and no output schema, the description fails to provide essential context about what fields get updated, error handling, or return values. It is insufficient for an AI agent to use correctly.

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 coverage is 100%, so the description doesn't need to add param details. It adds no additional meaning beyond what the schema already provides, earning the baseline score of 3.

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 tool updates an existing appointment, which distinguishes it from create and delete siblings. However, it doesn't specify which fields can be updated or differentiate from cancel_appointment.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives like cancel_appointment or create_appointment. No prerequisites or context provided.

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/andymillar84-cyber/mcp-cliniko'

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