Renaissance Dental Guide

get_appointment_link

Read-onlyIdempotent

Return a fallback public NexHealth scheduling link and phone only when the user needs to arrange a visit. For information questions, answer directly with the information tools. Does not read availability, hold a slot, submit a request, or confirm an appointment.

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": {
      "practice_id": "<practice_id>"
    },
    "name": "get_appointment_link"
  }
}

Input Schema

Name	Required	Description	Default
`practice_id`	Yes

Output Schema

Name	Required	Description	Default
`phone`	Yes
`source`	Yes
`next_step`	Yes
`booking_url`	Yes
`practice_id`	Yes
`practice_name`	Yes
`source_status`	Yes
`sources_checked`	Yes
`live_availability`	Yes
`appointment_created`	Yes
`information_may_be_outdated`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 24, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": false,
+  "properties": {
+    "appointment_created": {
+      "const": false
+    },
+    "booking_url": {
+      "type": "string"
+    },
+    "information_may_be_outdated": {
+      "type": "boolean"
+    },
+    "live_availability": {
+      "const": false
+    },
+    "next_step": {
+      "type": "string"
+    },
+    "phone": {
+      "type": "string"
+    },
+    "practice_id": {
+      "type": "string"
+    },
+    "practice_name": {
+      "type": "string"
+    },
+    "source": {
+      "type": "string"
+    },
+    "source_status": {
+      "type": "string"
+    },
+    "sources_checked": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "sources_checked",
+    "information_may_be_outdated",
+    "source_status",
+    "practice_id",
+    "practice_name",
+    "booking_url",
+    "phone",
+    "live_availability",
+    "appointment_created",
+    "next_step",
+    "source"
+  ],
+  "type": "object"
+}

First observedOct 24, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive behavior, but the description adds important scope details: it returns a fallback link and phone and does not read availability, hold slots, submit requests, or confirm appointments. It does not cover auth or rate limits, but for this simple read tool the added behavioral boundaries are substantial.

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 tightly written sentences with no filler. The intended use and scope limitations are front-loaded, and every sentence adds actionable guidance.

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?

The tool is simple, has a complete annotation profile, and includes an output schema, so the description need not explain return values. The description fully covers when to call it and which adjacent scheduling actions it does not perform.

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?

The description does not mention practice_id, and schema description coverage is 0%. However, the sole parameter is required and constrained by a single enum value, so the schema itself provides enough semantic context for a competent caller.

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 verb and resource: return a fallback public NexHealth scheduling link and phone. It also distinguishes itself from information-oriented siblings by directing information questions to the information tools.

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?

Explicitly says to use this only when the user needs to arrange a visit, and explicitly says to use information tools for information questions. It further clarifies what this tool does not do, removing ambiguity about adjacent scheduling actions.

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

All Renaissance Dental Guide 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?