tebra-mcp-server

Update Appointment

tebra_update_appointment

Idempotent

Update an existing Tebra appointment by changing only the fields you provide. Adjust scheduling, location, provider, mode, or notes; when changing start time, supply end time or duration.

Instructions

Update an existing appointment in Tebra. Only provided fields will be changed. When changing startDate, also provide endDate or duration. To only change the status, prefer tebra_update_appointment_status.

Input Schema

TableJSON Schema

Name	Required	Description
`notes`	No	Optional updated notes
`endDate`	No	Optional new end date/time (ISO 8601)
`duration`	No	Optional new duration in minutes (computes end time from startDate)
`patientId`	No	Patient ID (required by Tebra; auto-hydrated from the existing appointment if omitted)
`startDate`	No	Optional new start date/time (ISO 8601); provide endDate or duration with it
`providerId`	No	Optional new provider ID
`appointmentId`	Yes	Tebra appointment ID to update
`appointmentMode`	No	Optional new mode
`appointmentStatus`	No	Optional new status
`serviceLocationId`	No	Service location ID (required by Tebra; auto-hydrated from the existing appointment if omitted)
`confirmationStatus`	No	Deprecated alias for appointmentStatus
`appointmentReasonId`	No	Optional new appointment reason ID

Schema Changelog

Changes observed during successful MCP inspections.

Changed10 schema fields changedv0.6.0Sep 21, 2026

addedInput schema / properties / appointmentMode

Added value: +{
+  "description": "Optional new mode",
+  "enum": [
+    "InOffice",
+    "Telehealth"
+  ],
+  "type": "string"
+}

addedInput schema / properties / appointmentReasonId

Added value: +{
+  "description": "Optional new appointment reason ID",
+  "type": "string"
+}

addedInput schema / properties / appointmentStatus

Added value: +{
+  "description": "Optional new status",
+  "enum": [
+    "Unknown",
+    "Scheduled",
+    "ReminderSent",
+    "Confirmed",
+    "CheckedIn",
+    "Roomed",
+    "CheckedOut",
+    "NeedsReschedule",
+    "ReadyToBeSeen",
+    "NoShow",
+    "Cancelled",
+    "Rescheduled",
+    "Tentative"
+  ],
+  "type": "string"
+}

removedInput schema / properties / cancellationReason

Removed value: -{
-  "description": "Optional cancellation reason (for cancelled appointments)",
-  "type": "string"
-}

changedInput schema / properties / confirmationStatus / description

Previous value: -"Optional new confirmation status"New value: +"Deprecated alias for appointmentStatus"

changedInput schema / properties / duration / description

Previous value: -"Optional new duration in minutes"New value: +"Optional new duration in minutes (computes end time from startDate)"

addedInput schema / properties / endDate

Added value: +{
+  "description": "Optional new end date/time (ISO 8601)",
+  "type": "string"
+}

addedInput schema / properties / patientId

Added value: +{
+  "description": "Patient ID (required by Tebra; auto-hydrated from the existing appointment if omitted)",
+  "type": "string"
+}

addedInput schema / properties / serviceLocationId

Added value: +{
+  "description": "Service location ID (required by Tebra; auto-hydrated from the existing appointment if omitted)",
+  "type": "string"
+}

changedInput schema / properties / startDate / description

Previous value: -"Optional new start date/time (ISO 8601)"New value: +"Optional new start date/time (ISO 8601); provide endDate or duration with it"

First observedv0.2.5Jun 14, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already indicate the tool is not read-only and not destructive. The description adds the partial-update behavior ('Only provided fields will be changed') and the dependency between startDate and endDate/duration, which are not covered by annotations. This adds useful behavioral context without contradiction.

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?

Two sentences with no filler. The purpose, partial-update behavior, parameter dependency, and sibling preference are all front-loaded and clearly separated. Every sentence earns its place.

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 tool with 12 parameters but full schema coverage and no output schema, the description covers the essential usage nuances: partial updates, the startDate dependency, and the status-only alternative. It does not explain return values, but that is not required without an output schema. It is sufficient for an agent to call it correctly.

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 description coverage is 100%, so all parameters are already documented. The description adds the key rule that changing startDate requires endDate or duration, which is not in the schema. This extra guidance raises the value beyond the baseline for high coverage.

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?

Clearly states the tool updates an existing appointment in Tebra and distinguishes itself from the sibling tebra_update_appointment_status by explicitly preferring that tool for status-only changes. The verb 'update' and resource 'appointment' are specific and unambiguous.

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?

Provides explicit guidance: when changing startDate, also provide endDate or duration, and when only changing status, prefer a different tool. This directly tells an agent when to use this tool versus an alternative.

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

Deploy Server

Update Appointment

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools