DodoDentist Dental Clinic

Book a dental appointment

book_appointment

DestructiveIdempotent

Use this when someone asks to book a patient in at their dental practice. Returns the new appointment with its time, providers and how many procedures it holds; it takes the practice's usual length, seat and reminders, so the practice's reminder messages go to the patient. Not for finding free slots.

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>",
      "startTime": "<startTime>",
      "requestId": "<requestId>"
    },
    "name": "book_appointment"
  }
}

Input Schema

Name	Required	Description
`clinicId`	No	Id of the practice, from list_clinics. Leave it out when the user has one practice.
`patientId`	Yes	Id of the patient, from find_patient or create_patient.
`requestId`	Yes	A unique id you choose for this booking, such as a UUID. Calling again with the same requestId returns the first booking instead of booking twice.
`startTime`	Yes	Start as an ISO 8601 time with the practice's UTC offset, such as 2026-11-20T10:00:00+01:00.
`providerIds`	No	Ids of the dentists, nurses or assistants who take it, from list_clinic_providers. Leave it out when the practice has one, or the user takes appointments.
`procedureIds`	No	Ids of the treatments booked, from list_procedures.
`durationMinutes`	No	Length in minutes. Leave it out for the practice's usual length.

Output Schema

Name	Required	Description	Default
`status`	Yes
`appointment`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 8, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=true, idempotentHint=true and openWorldHint=true, so the safety profile is covered. The description adds real value beyond that: it previews the return payload and explains that practice defaults (usual length, seat, reminders) are applied and that reminder messages go to the patient. It could have said more about failure modes, such as what happens if the slot is taken.

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?

Three sentences, front-loaded with the usage trigger, with zero filler about generic capability. The middle sentence is long and carries several distinct facts (return shape, defaults, reminders) that would read better separated, but nothing is wasted.

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?

With seven parameters, three required, and an output schema that already covers return values, the description covers the essentials: trigger, exclusion, defaults applied, and side effects on patient messaging. What's missing is conflict handling and whether a resulting notification is sent immediately, which matters for a destructive-flagged booking tool.

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 clinicId, patientId, providerIds and procedureIds with their source tools, is already documented in the schema. The description only reinforces the defaults idea ('takes the practice's usual length, seat and reminders'), which lightly supports durationMinutes being optional. Baseline 3 is appropriate since the schema does the heavy lifting.

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 opens with a specific verb and resource: booking a patient into a dental practice, and it goes further by stating what is returned (the new appointment with its time, providers and procedure count). It also carves out scope against a sibling with 'Not for finding free slots', so an agent can distinguish it from get_clinic_availability 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 Guidelines4/5

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

It gives an explicit usage trigger ('when someone asks to book a patient in at their dental practice') and one explicit exclusion ('Not for finding free slots'). It doesn't mention adjacent mutations like reschedule_appointment or cancel_appointment, so the routing guidance is clear but not exhaustive.

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?