Xona Dental Gateway

Hold an open time and text the patient a link

hold_xona_booking_slot

Hold one open time and text the patient a link to it. The page the link opens shows the time and the details above a Book this appointment button. When the patient presses it the appointment is booked, or, at a practice that confirms bookings itself, sent to the practice as a request.

Input Schema

TableJSON Schema

Name	Required	Description
`date`	Yes	The chosen slot's date exactly as list_xona_booking_slots returned it
`note`	No
`last_name`	Yes	The patient's last name, as the patient gave it in this conversation
`first_name`	Yes	The patient's first name, as the patient gave it in this conversation
`service_id`	Yes
`date_of_birth`	Yes	The patient's date of birth, as the patient gave it in this conversation
`guardian_name`	No	Required when the patient is under 16
`patient_phone`	Yes	The patient's own Canadian or US mobile number, as the patient gave it in this conversation; the booking link is texted there
`practice_slug`	Yes
`slot_fingerprint`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
`reason`	No
`outcome`	No
`practice`	Yes
`action_id`	Yes
`next_step`	Yes
`booking_url`	No
`continue_url`	No
`verification`	No
`booking_steps`	No
`hold_expires_at`	No
`link_expires_at`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedSep 27, 2026

addedInput schema / properties / date_of_birth / description

Added value: +"The patient's date of birth, as the patient gave it in this conversation"

addedInput schema / properties / first_name / description

Added value: +"The patient's first name, as the patient gave it in this conversation"

addedInput schema / properties / last_name / description

Added value: +"The patient's last name, as the patient gave it in this conversation"

changedInput schema / properties / patient_phone / description

Previous value: -"The patient's own Canadian or US mobile number; the booking link is texted there"New value: +"The patient's own Canadian or US mobile number, as the patient gave it in this conversation; the booking link is texted there"

Changed10 schema fields changedSep 23, 2026

removedInput schema / properties / patient_email

Removed value: -{
-  "description": "The patient's own email; the first link goes there",
-  "format": "email",
-  "maxLength": 254,
-  "minLength": 3,
-  "type": "string"
-}

changedInput schema / properties / patient_phone / description

Previous value: -"The patient's mobile number; the second link is texted there once the email link is tapped"New value: +"The patient's own Canadian or US mobile number; the booking link is texted there"

changedInput schema / required

Previous value: -[
-  "practice_slug",
-  "service_id",
-  "slot_fingerprint",
-  "date",
-  "patient_email",
-  "patient_phone",
-  "first_name",
-  "last_name",
-  "date_of_birth"
-]New value: +[
+  "practice_slug",
+  "service_id",
+  "slot_fingerprint",
+  "date",
+  "patient_phone",
+  "first_name",
+  "last_name",
+  "date_of_birth"
+]

addedOutput schema / properties / booking_url
```
Added value: +{
+  "type": "string"
+}
```
removedOutput schema / properties / consent_text
```
Removed value: -{
-  "type": "string"
-}
```
removedOutput schema / properties / consent_version
```
Removed value: -{
-  "type": "string"
-}
```

addedOutput schema / properties / link_expires_at

Added value: +{
+  "format": "date-time",
+  "type": "string"
+}

addedOutput schema / properties / outcome
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / reason
```
Added value: +{
+  "type": "string"
+}
```

changedOutput schema / required

Previous value: -[
-  "action_id",
-  "practice",
-  "hold_expires_at",
-  "verification",
-  "consent_version",
-  "consent_text",
-  "booking_steps",
-  "next_step"
-]New value: +[
+  "action_id",
+  "practice",
+  "next_step"
+]

First observedSep 18, 2026

TDQS

B3.2/5.0

Behavior4/5

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

The description adds substantial behavioral context beyond the annotations: it texts the patient, opens a page with a Book this appointment button, and either books directly or sends a request depending on the practice. It does not mention hold expiry, idempotency, or auth requirements, but the annotations already cover basic read/write and destructive hints.

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?

The description is front-loaded with the core action and uses three sentences without obvious repetition. The middle sentence about the link page is somewhat detailed but useful for understanding the downstream flow.

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

Completeness3/5

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

For a 10-parameter mutation tool with an output schema and 60% schema coverage, the description covers the patient-facing flow well but omits prerequisites, parameter sourcing, and operational constraints like hold expiry or idempotency. It is minimally adequate rather than complete.

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

Parameters2/5

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

Schema description coverage is 60%, with several important parameters such as service_id, practice_slug, slot_fingerprint, and note lacking schema descriptions. The tool description adds no parameter-level meaning at all, so it fails to compensate for the coverage gap.

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 states a specific verb and resource: hold one open time and text the patient a link. It clearly implies a pre-booking hold step, but it does not explicitly distinguish itself from siblings such as confirm_xona_booking or abandon_xona_booking.

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?

The description explains what happens after the patient receives the link, but gives no explicit guidance on when to call this tool versus list_xona_booking_slots, confirm_xona_booking, or abandon_xona_booking. It also does not state prerequisites such as needing a slot_fingerprint from a prior list operation.

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

All Xona Dental Gateway 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?