Skip to main content
Glama

Xona Dental Gateway

by com.xonark
OverviewDiscussionsAdmin

Choose a time to book at a clinic

choose_public_booking_time

For a public_provider_booking action: keeps one time from list_public_booking_slots (or a soonest search row's earliest) and returns continue_url, Xona's page where the patient enters their own details and presses Book. Xona then books that time in the clinic's own scheduler. It takes the action and the time (service_id, slot_id, starts_at) only, reads that time again and keeps it only if it is still open; the page collects the patient's details.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
slot_idYesThe chosen time's id from list_public_booking_slots (slot_id on a soonest row's earliest).
action_idYes
starts_atYesThe chosen time's starts_at, exactly as returned.
service_idYesThe chosen time's service_id.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
bookingYes
next_stepYes
continue_urlYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • addedInput schema / properties / service_id
      Added value: +{
+  "description": "The chosen time's service_id.",
+  "maxLength": 160,
+  "minLength": 1,
+  "type": "string"
+}
    • changedInput schema / properties / slot_id / description
      Previous value: -"The id of one time from this action's latest list_public_booking_slots result."New value: +"The chosen time's id from list_public_booking_slots (slot_id on a soonest row's earliest)."
    • changedInput schema / properties / slot_id / maxLength
      Previous value: -160New value: +256
    • addedInput schema / properties / starts_at
      Added value: +{
+  "description": "The chosen time's starts_at, exactly as returned.",
+  "format": "date-time",
+  "maxLength": 64,
+  "type": "string"
+}
    • changedInput schema / required
      Previous value: -[
-  "action_id",
-  "slot_id"
-]New value: +[
+  "action_id",
+  "service_id",
+  "slot_id",
+  "starts_at"
+]
  2. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations cover the safety profile (readOnlyHint=false, idempotentHint=false), and the description adds genuinely useful behavior beyond that: it re-reads the slot and keeps it only if still open, and it discloses that Xona performs the actual booking while the patient enters details on the returned page. This is the kind of state/flow detail annotations cannot convey.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two long, clause-heavy sentences that are front-loaded with the flow but include redundancy ('the page collects the patient's details' is stated twice in substance) and a run-on structure that slows parsing.

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?

For a step in a multi-tool booking workflow with an output schema present, the description covers the key context: input source, re-validation behavior, and what continue_url is for. Return-value details are correctly left to the output schema.

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 75%, so most parameters are already documented, but the description adds meaning by grouping service_id/slot_id/starts_at as 'the time' and including action_id in the call shape, plus stressing starts_at must match the returned value exactly. It adds value over the schema without fully substituting for the undocumented action_id semantics.

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 (keeps a chosen time) and resource (a public booking slot), and explicitly frames it as the step following list_public_booking_slots. It distinguishes itself from that sibling by noting it selects rather than lists, though the phrasing is dense enough that the core action takes a second read.

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 clearly scopes usage to a 'public_provider_booking action' and names the upstream source of the time (list_public_booking_slots or a soonest search row's earliest). No explicit when-not or exclusions are given, but the sequencing context is clear.

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 toolsInspect
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