DodoDentist Dental Clinic

Add a dental patient

create_patient

DestructiveIdempotent

Use this when someone asks to add a new patient to their dental practice. Returns the patient's id, name, practice and language; the phone and email given are saved but never returned, and nothing clinical is taken. Not for changing an existing 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": {
      "name": "<name>",
      "requestId": "<requestId>"
    },
    "name": "create_patient"
  }
}

Input Schema

Name	Required	Description
`name`	Yes	The patient's full name.
`email`	No	Email address.
`phone`	No	Mobile number, with the country code when known.
`clinicId`	No	Id of the practice, from list_clinics. Leave it out when the user has one practice.
`language`	No	Language for their messages, as a code such as en, it or pt-BR. Defaults to the practice language.
`requestId`	Yes	A unique id you choose for this patient, such as a UUID. Calling again with the same requestId returns the first patient instead of adding a second one.

Output Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 8, 2026

TDQS

A4.7/5.0

Behavior4/5

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

Beyond the annotations, it discloses what is returned (id, name, practice, language), that phone and email are stored but never echoed back, and that no clinical data is captured. It does not address permissions or the noteworthy destructiveHint=true declared in annotations, so it stops short of full behavioral coverage.

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?

Three sentences, front-loaded with the trigger condition, then return behavior, then the exclusion. No filler and nothing repeated from the title.

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

Completeness5/5

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

Covers trigger, exclusions, return contents, side effects on hidden fields, and data-scope limits, which is everything an agent needs for a create tool with 6 params. Mentioning return fields is mildly redundant with the output schema but not harmful.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3; the description adds genuine meaning by explaining that phone and email are write-only fields that are saved but never returned. It does not touch clinicId, language, or requestId semantics, which the schema already handles well.

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?

States a specific verb and resource ("add a new patient to their dental practice") and explicitly scopes out the nearest sibling with "Not for changing an existing patient." An agent can distinguish this from update_patient without opening either 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?

The first sentence gives a concrete triggering condition ("when someone asks to add a new patient") and the last sentence gives an explicit exclusion for existing patients. When-to-use and when-not-to-use are both present.

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?