Skip to main content
Glama
andymillar84-cyber

mcp-cliniko

get_patient

Fetch a patient's complete record from Cliniko by providing their unique ID.

Instructions

Get a specific patient by ID

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
patient_idYesPatient ID

Implementation Reference

  • The get_patient tool handler: receives patient_id, calls client.getPatient(), and returns the patient as JSON.
    // Get patient by ID
    server.tool('get_patient', {
      description: 'Get a specific patient by ID',
      inputSchema: {
        type: 'object',
        properties: {
          patient_id: { type: 'number', description: 'Patient ID' }
        },
        required: ['patient_id']
      },
    }, async ({ patient_id }: { patient_id: number }) => {
      try {
        const patient = await client.getPatient(patient_id);
        return {
          content: [{
            type: 'text',
            text: JSON.stringify(patient, null, 2)
          }]
        };
      } catch (error) {
        throw new Error(`Failed to get patient: ${error instanceof Error ? error.message : 'Unknown error'}`);
      }
    });
  • Input schema for get_patient: requires a patient_id (number).
    server.tool('get_patient', {
      description: 'Get a specific patient by ID',
      inputSchema: {
        type: 'object',
        properties: {
          patient_id: { type: 'number', description: 'Patient ID' }
        },
        required: ['patient_id']
      },
  • src/index.ts:58-58 (registration)
    Registration call: registerPatientTools(toolRegistry, clinikoClient) is invoked at server startup.
    registerPatientTools(toolRegistry, clinikoClient);
  • Export function registerPatientTools that registers the tool on the server.
    export function registerPatientTools(server: any, client: ClinikoClient) {
  • Helper method getPatient(id) on ClinikoClient: makes a GET request to /patients/{id} and returns a Patient.
    async getPatient(id: number): Promise<Patient> {
      return this.request<Patient>(`/patients/${id}`);
    }
Behavior2/5

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

With no annotations, the description must disclose behavioral traits. It only states 'Get' implying idempotent read, but does not mention error behavior (e.g., if ID not found), authentication requirements, or whether the response is a full patient object. Minimal disclosure.

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 sentence with no extraneous words, front-loaded with the verb and resource. Efficient and clear.

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 is simple (single required parameter, no output schema), the description should still specify what is returned (e.g., patient details). It fails to mention the response format, leaving the agent uncertain about the tool's output.

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 input schema covers 100% of parameters with description 'Patient ID'. The description echoes 'by ID' but adds no additional meaning beyond the schema. Baseline score of 3 applies.

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 'Get' and the resource 'specific patient by ID'. It is unambiguous, but does not differentiate from sibling tools like 'get_appointment' or 'get_invoice', which have similar structure.

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 vs alternatives such as 'list_patients' or 'create_patient'. No when-not-to-use or preconditions 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