DodoDentist Dental Clinic

Update a patient's details

update_patient

DestructiveIdempotent

Use this when someone asks to change a patient's name, phone, email or language. Returns the patient's id, name, practice and which fields changed; contact details are never returned. Not for clinical records or adding a new patient.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "patientId": "<patientId>",
      "expectedLastEditTime": "<expectedLastEditTime>"
    },
    "name": "update_patient"
  }
}

Input Schema

Name	Required	Description
`name`	No	New full name.
`email`	No	New email address.
`phone`	No	New mobile number, with the country code when known.
`language`	No	New language for their messages, as a code such as en or it.
`patientId`	Yes	Id of the patient, from find_patient.
`expectedLastEditTime`	Yes	The lastEditTime from find_patient. A patient changed since then is refused.

Output Schema

Name	Required	Description	Default
`status`	Yes
`patient`	Yes
`changedFields`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 8, 2026

TDQS

A4.1/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=true and idempotentHint=true, so the mutation profile is covered structurally. The description adds a valuable privacy constraint (contact details are never returned) and the return shape, but it does not address the overwrite semantics implied by destructiveHint=true or the concurrency-refusal path, which appear only in the schema.

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?

Two dense sentences with zero filler: trigger first, exclusions last. The parenthetical on the return payload is compact and earns its place, though it slightly competes with the output schema for space.

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

Completeness4/5

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

For a 6-parameter mutation with full schema coverage, an output schema, and rich annotations, the description covers purpose, exclusions and output expectations. The remaining gap is whether omitting an optional field leaves it unchanged or clears it, which matters given destructiveHint=true.

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 every parameter including patientId and expectedLastEditTime is already documented (including the optimistic-concurrency refusal). The description only echoes the four writable fields, adding no format or constraint detail beyond the schema; baseline 3 applies.

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?

The description gives a specific verb (change) plus the exact updatable fields (name, phone, email, language) on a named resource, and explicitly excludes clinical records and creating a new patient. This makes it distinguishable from create_patient and any clinical-record sibling without opening a schema.

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

Usage Guidelines5/5

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

It opens with an explicit trigger ("Use this when someone asks to change...") and closes with explicit exclusions ("Not for clinical records or adding a new patient"), which points the agent at create_patient for the add case. Little is left to inference.

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

All DodoDentist Dental Clinic tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?