DodoDentist Dental Clinic

Find appointments

list_appointments

Read-onlyIdempotent

Use this when someone asks when a patient is booked or what is booked on a day, or an appointment id is needed to move or cancel it. Returns up to 50 appointments in start order with id, patient and provider ids, times, status and edit time, for one day or one patient. Not for counting how busy days are, nor for procedures, notes or clinical details.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_appointments"
  }
}

Input Schema

Name	Required	Description
`endTime`	No	End of the window. Without a patientId at most one day after the start, and one day by default; with one at most a year, and 90 days by default
`clinicId`	No	Only this practice; every practice of the account when absent
`patientId`	No	Only this patient, by the id find_patient returns
`startTime`	No	Start of the window as an ISO 8601 time with the practice's UTC offset; defaults to now

Output Schema

Name	Required	Description
`count`	Yes
`range`	Yes
`hasMore`	Yes	More appointments fall in the window than were returned
`appointments`	Yes	Appointments in start order, canceled ones included, that the signed-in account can view. Procedures, notes, findings, treatments and patient names are never returned.

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 8, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent and non-destructive, so safety is covered; the description adds the non-obvious result cap of 50, start-time ordering, and the breadth constraint (one day or one patient). The field list partially duplicates the output schema, which keeps this from a 5.

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 tight sentences: trigger first, then return shape and scope, then exclusions. Nothing redundant, and the most decision-relevant information (when to pick this tool) is front-loaded.

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?

With rich annotations, a fully described 4-parameter schema, and an output schema covering the returned fields, the description supplies exactly the missing layer: selection criteria, result cap, ordering, and scope limits. An agent has everything needed to call it correctly.

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 the one-day/one-year window limits and clinicId scoping) is already documented in the schema. The description only echoes the 'one day or one patient' scoping at a high level and says nothing about clinicId or default window behavior beyond what the schema states. 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?

States a specific resource (appointments) with concrete query modes ('what is booked on a day' / 'when a patient is booked') and even the downstream reason an id is needed ('to move or cancel it'). It explicitly carves out what it is not (counting busy days, procedures, notes, clinical details), which separates it from get_clinic_schedule_summary and list_procedures 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?

Gives explicit when-to-use triggers (patient booking questions, day-at-a-glance, needing an id for reschedule/cancel) and explicit when-not-to-use exclusions (busy-day counting, procedures, notes). The alternative for the excluded counting case is nameable from the sibling list, so routing is unambiguous.

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?