Skip to main content
Glama

update_patient

Modify patient details in Cliniko, including contact information, demographics, and medical identifiers, to maintain accurate healthcare records.

Instructions

Update an existing patient

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
patient_idYesPatient ID
first_nameNoPatient first name
last_nameNoPatient 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
Behavior2/5

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

With no annotations provided, the description carries full burden but only states the basic action ('update') without disclosing behavioral traits like permission requirements, whether updates are partial or full, side effects on related data, or error handling. This is inadequate for a mutation tool with complex parameters.

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, efficient sentence with no wasted words, making it easy to parse. It is front-loaded with the core action, though it could benefit from more detail given the tool's complexity.

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?

For a mutation tool with 17 parameters, no annotations, and no output schema, the description is insufficient. It lacks details on behavior, return values, error cases, and how it differs from siblings, leaving significant gaps for an AI agent to operate effectively.

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 the schema fully documents all 17 parameters. The description adds no additional meaning beyond implying that parameters correspond to patient attributes, which the schema already covers. This meets the baseline for high schema coverage.

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 action ('update') and resource ('existing patient'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'create_patient' or 'get_patient' beyond the verb choice, missing explicit distinction about modifying versus creating or retrieving.

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 such as 'create_patient' for new patients or 'get_patient' for retrieval. The description lacks context about prerequisites, error conditions, or typical use cases, leaving the agent without usage direction.

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

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