Skip to main content
Glama
andymillar84-cyber

mcp-cliniko

delete_appointment

Delete an appointment from your healthcare practice management system by providing the appointment ID.

Instructions

Delete an appointment completely

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
appointment_idYesAppointment ID

Implementation Reference

  • Registration of the 'delete_appointment' MCP tool with its input schema (appointment_id required) and handler that calls client.deleteAppointment
    // Delete appointment
    server.tool('delete_appointment', {
      description: 'Delete an appointment completely',
      inputSchema: {
        type: 'object',
        properties: {
          appointment_id: { type: 'number', description: 'Appointment ID' }
        },
        required: ['appointment_id']
      },
    }, async ({ appointment_id }: { appointment_id: number }) => {
      try {
        await client.deleteAppointment(appointment_id);
        return {
          content: [{
            type: 'text',
            text: `Appointment ${appointment_id} has been deleted successfully`
          }]
        };
      } catch (error) {
        throw new Error(`Failed to delete appointment: ${error instanceof Error ? error.message : 'Unknown error'}`);
      }
    });
  • Handler function for delete_appointment: extracts appointment_id, calls client.deleteAppointment, returns success message, or throws on error
    }, async ({ appointment_id }: { appointment_id: number }) => {
      try {
        await client.deleteAppointment(appointment_id);
        return {
          content: [{
            type: 'text',
            text: `Appointment ${appointment_id} has been deleted successfully`
          }]
        };
      } catch (error) {
        throw new Error(`Failed to delete appointment: ${error instanceof Error ? error.message : 'Unknown error'}`);
      }
    });
  • Input schema for delete_appointment: expects a single required 'appointment_id' parameter of type number
    inputSchema: {
      type: 'object',
      properties: {
        appointment_id: { type: 'number', description: 'Appointment ID' }
      },
      required: ['appointment_id']
    },
  • ClinikoClient.deleteAppointment: makes a DELETE request to /appointments/{id} and handles 204 No Content response
    async deleteAppointment(id: number): Promise<void> {
      return this.request<void>(`/appointments/${id}`, {
        method: 'DELETE',
      });
    }
  • src/index.ts:59-59 (registration)
    Tool registration entry point in index.ts: calls registerAppointmentTools to register all appointment tools including delete_appointment
    registerAppointmentTools(toolRegistry, clinikoClient);
Behavior2/5

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

With no annotations, the description should disclose behavioral traits such as irreversibility, required permissions, or side effects. 'Delete an appointment completely' only implies deletion but provides no further context.

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?

The description is extremely concise with a single sentence. It is front-loaded and wastes no words, but could be slightly more structured with additional context.

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 low complexity (1 parameter, no output schema), the description is minimally adequate but lacks behavioral context (e.g., whether deletion is permanent). It does not fully compensate for missing annotations.

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% (appointment_id is described). The description adds no additional meaning beyond the schema, so a baseline score of 3 is appropriate.

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 'Delete' and resource 'appointment', making the purpose unambiguous. However, it does not distinguish from the sibling tool 'cancel_appointment', which might have a similar effect.

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 is provided on when to use this tool versus alternatives like 'cancel_appointment'. No conditions or exclusions are mentioned, leaving the agent to guess.

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