Skip to main content
Glama

create_patient

Add new patients to the Cliniko healthcare system by entering personal details, contact information, and medical identifiers for practice management.

Instructions

Create a new patient

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
first_nameYesPatient first name
last_nameYesPatient last name
titleNoTitle (Mr, Ms, Dr, etc)
preferred_nameNoPreferred name
date_of_birthNoDate of birth (YYYY-MM-DD)
sexNoBiological sex
emailNoEmail address
phone_numberNoPrimary phone number
address_line_1NoAddress line 1
address_line_2NoAddress line 2
suburbNoSuburb/City
postcodeNoPostcode
stateNoState/Province
countryNoCountry
medicare_numberNoMedicare number
medicare_reference_numberNoMedicare reference number

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.7/5.0
Behavior1/5

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

No annotations provided, and description fails to disclose behavioral traits like success response, error conditions, or side effects beyond the bare action.

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

Conciseness3/5

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

Extremely concise (one sentence) but too terse; lacks essential information for a tool with 16 parameters and no annotations.

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

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given 16 parameters, no output schema, and no annotations, the description is severely incomplete, omitting return values, prerequisites, and behavioral details.

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% with descriptions for all parameters; description adds no extra meaning, defaulting to baseline 3.

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?

Description clearly states 'Create a new patient', with a specific verb and resource, differentiating from siblings like update_patient or delete_patient.

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 such as update_patient or create_appointment; lacks context for appropriate use.

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