Skip to main content
Glama
jamesrosing

tebra-mcp-server

by jamesrosing
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Get Appointment Detail

tebra_get_appointment_detail
Read-only

Get complete appointment details by ID, including recurrence rules, group data, and all resource slots.

Instructions

Get full detail for a single appointment by ID, including recurrence rules, group data, and all resource slots.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fieldsNoOptional list of result fields to return (dotted paths for nested values, e.g. "cases.policies.companyName"). Omit for the default field set. Request only the fields you need — results contain protected health information.
appointmentIdYesTebra appointment ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.6.0
    • addedInput schema / properties / fields
      Added value: +{
+  "description": "Optional list of result fields to return (dotted paths for nested values, e.g. \"cases.policies.companyName\"). Omit for the default field set. Request only the fields you need — results contain protected health information.",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}
  2. First observedv0.2.5

TDQS

A4.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, and the description does not contradict this. It adds details about the response content (recurrence rules, group data, resource slots) but does not disclose additional behavioral traits such as authentication requirements, rate limits, or side effects. Since the annotations cover the read-only aspect, a 3 is appropriate for adding only marginal behavioral context.

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?

A single sentence that front-loads the verb and resource, then packs the key inclusion details. There is zero waste; every word adds value.

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?

For a read-only single-resource tool with two well-documented parameters and no output schema, the description fully covers what the agent needs to call it correctly: it specifies the identifier and the type of data returned. Nothing essential is missing.

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?

Schema description coverage is 100%: both parameters (appointmentId and fields) have descriptions in the schema. The tool description does not add extra parameter-level meaning beyond what the schema already provides, so the baseline of 3 applies. The fields parameter's PHI warning is already in the schema description, not the tool description.

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 a specific verb ('Get') with a clear resource ('full detail for a single appointment by ID') and enumerates the included content (recurrence rules, group data, resource slots), distinguishing it from sibling tools like tebra_get_appointments that list appointments. It is immediately clear what the tool does and how it differs from a list operation.

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 implies usage: this tool is for retrieving the full detail of a single appointment by ID, while tebra_get_appointments likely handles listing. It provides clear context for when to use it but does not explicitly name alternatives or state when not to use it, so it falls short of a 5.

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