Skip to main content
Glama
jamesrosing

tebra-mcp-server

by jamesrosing
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Create Appointment Reason

tebra_create_appointment_reason

Create a new appointment reason in Tebra by specifying its name and default duration. Optionally set a color code for easy identification.

Instructions

Create a new appointment reason in Tebra with name and default duration. Color is a Tebra color code number (not hex).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesAppointment reason name
colorNoOptional Tebra color code (integer)
durationYesDefault duration in minutes
practiceIdNoOptional practice ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.6.0
    • removedInput schema / properties / category
      Removed value: -{
-  "description": "Optional category",
-  "type": "string"
-}
    • changedInput schema / properties / color / description
      Previous value: -"Optional color code (hex or named color)"New value: +"Optional Tebra color code (integer)"
    • changedInput schema / properties / color / type
      Previous value: -"string"New value: +"number"
    • addedInput schema / properties / practiceId
      Added value: +{
+  "description": "Optional practice ID",
+  "type": "string"
+}
  2. First observedv0.2.5

TDQS

A4/5.0
Behavior3/5

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

Annotations already indicate readOnlyHint=false and destructiveHint=false. The description adds a useful clarification about the color format, but does not disclose other behavioral aspects such as potential duplicate handling, output/return behavior, or authentication requirements. There is no contradiction with annotations.

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 two sentences with no filler. It front-loads the purpose and includes only the most important non-obvious parameter detail (color format). Every word 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 simple creation tool with rich schema descriptions and annotations, the description covers what is needed. It lacks an explicit note about return values or unique constraints, but the verb 'Create' plus the schema and annotations give sufficient context for correct invocation.

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 100%, so baseline is 3. The description adds extra meaning by clarifying that color is a Tebra color code number, not hex, which goes beyond the schema's 'Optional Tebra color code (integer)'. The other parameters are adequately described in the schema.

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 states a specific action ('Create') and resource ('appointment reason') with the key fields involved. It clearly differentiates from sibling create tools like tebra_create_appointment and tebra_create_patient by naming the unique resource.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage when a new appointment reason is needed, but it does not explicitly state when to use this tool over alternatives or mention related tools like tebra_get_appointment_reasons for checking existing reasons. No exclusions or prerequisites are provided.

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

Deploy Server

Other Tools