Xona Dental Gateway

Give up a booking that is not booked yet

abandon_xona_booking

Idempotent

Release the held time and drop the patient's details when the patient no longer wants it, at any step before it is booked. It never cancels a booked appointment. Calling again returns the same result.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`action_id`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
`reason`	No
`outcome`	Yes
`practice`	Yes
`action_id`	Yes
`next_step`	Yes
`booking_url`	No
`continue_url`	No
`booking_steps`	No
`consent_version`	No
`link_expires_at`	No
`confirmation_sms`	No
`appointment_start`	No
`appointment_start_local`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedSep 23, 2026

addedOutput schema / properties / booking_steps

Added value: +{
+  "items": {
+    "properties": {
+      "patient_does": {
+        "type": "string"
+      },
+      "patient_provides": {
+        "items": {
+          "type": "string"
+        },
+        "type": "array"
+      },
+      "status": {
+        "enum": [
+          "done",
+          "waiting_for_patient",
+          "not_started"
+        ],
+        "type": "string"
+      },
+      "step": {
+        "type": "integer"
+      },
+      "tool": {
+        "type": "string"
+      },
+      "xona_sends": {
+        "properties": {
+          "channel": {
+            "type": "string"
+          },
+          "contains": {
+            "type": "string"
+          },
+          "link_expires_at": {
+            "format": "date-time",
+            "type": "string"
+          },
+          "to": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "channel"
+        ],
+        "type": "object"
+      }
+    },
+    "required": [
+      "step",
+      "status"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}

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

addedOutput schema / properties / link_expires_at

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

changedOutput schema / required

Previous value: -[
-  "action_id",
-  "practice",
-  "next_step"
-]New value: +[
+  "action_id",
+  "practice",
+  "outcome",
+  "next_step"
+]

First observedSep 18, 2026

TDQS

A3.8/5.0

Behavior4/5

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

The description adds behavioral detail beyond the annotations: it reveals that the tool releases a hold and drops patient details, and that it is safe to call repeatedly ('Calling again returns the same result'), which enriches the idempotentHint annotation. It also clarifies scope with 'never cancels a booked appointment', aligning with destructiveHint false.

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?

The description is three short sentences with no filler. The primary action and scope are front-loaded, the exclusion is stated clearly, and the idempotency note is concise. Every sentence earns its place.

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 single-parameter tool with an output schema and idempotency annotation, the description covers the main behavior, scope, and repeated-call behavior. However, it leaves out the crucial meaning of action_id and does not say it should be the identifier returned by a prior hold action, which an agent needs to invoke the tool correctly.

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

Parameters1/5

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

The schema has a single required parameter, action_id, with 0% schema description coverage. The description never explains what action_id refers to, how to obtain it, or what format is expected beyond the schema constraints. Since the schema coverage is low, the description was responsible for compensating and it does not.

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 uses specific verbs ('Release', 'drop') tied to a clear resource ('the held time', 'the patient's details') and states exactly when it applies ('at any step before it is booked'). It also distinguishes itself from cancellation by explicitly saying 'It never cancels a booked appointment', separating it from any cancellation sibling.

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?

The description clearly states when to use the tool: when the patient no longer wants the held time before it is booked. It also provides a strong exclusion: it is not for booked appointments. It does not name an explicit alternative tool, but the context and exclusion are enough for an agent to select it appropriately.

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?