Skip to main content
Glama
jamesrosing

tebra-mcp-server

by jamesrosing
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Get Patient

tebra_get_patient
Read-only

Retrieve a full patient record by Tebra patient ID or external system ID, including demographics, contact info, cases, insurance policies, and authorizations. Request only needed fields to limit protected health information.

Instructions

Get a full patient record from Tebra by patient ID, or by external system ID (optionally scoped to an external vendor). Includes demographics, contact info, cases, insurance policies, and authorizations. Insurance policy and group numbers are omitted unless named in fields.

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.
patientIdNoTebra patient ID (numeric)
externalIdNoExternal system ID (alternative to patientId)
externalVendorIdNoOptional external vendor ID to scope the externalId lookup

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv0.6.0
    • addedInput schema / properties / externalId
      Added value: +{
+  "description": "External system ID (alternative to patientId)",
+  "type": "string"
+}
    • addedInput schema / properties / externalVendorId
      Added value: +{
+  "description": "Optional external vendor ID to scope the externalId lookup",
+  "type": "string"
+}
    • 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"
+}
    • changedInput schema / properties / patientId / description
      Previous value: -"Tebra patient ID"New value: +"Tebra patient ID (numeric)"
    • changedInput schema / required
      Previous value: -[
-  "patientId"
-]New value: +[]
  2. First observedv0.2.5

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true; the description adds a genuinely non-obvious data-visibility quirk: 'Insurance policy and group numbers are omitted unless named in fields'. This materially affects what the agent receives. It does not disclose error behavior or identifier-precedence semantics, but for a read-only fetch the disclosure is strong.

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 sentences, front-loaded with the action and identifier alternatives, then return contents, then the sensitive-data caveat. Every sentence earns its place with no filler or repetition of schema text.

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 read-only fetch with four well-documented parameters, the description covers return content categories and the fields caveat, and the annotations carry the safety profile. The main gap is the identifier requirement: required is empty and the description does not state that exactly one of patientId/externalId should be supplied or what happens if both are passed.

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 the baseline is 3; the description adds meaning by tying the fields parameter to the insurance/group-number omission behavior and by framing externalVendorId as optionally scoping the externalId lookup. It stops short of explaining precedence if both patientId and externalId are supplied, which the required:[] schema leaves ambiguous.

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: 'Get a full patient record from Tebra' by patientId or externalId. The scope phrase 'full patient record' plus the listed contents (demographics, contact, cases, insurance, authorizations) distinguishes it from subset siblings like tebra_get_patient_authorizations and from search/bulk tools. Clear and actionable without needing to open the schema.

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 lookup methods ('by patient ID, or by external system ID') imply when the tool applies, but there is no explicit when-to-use vs alternatives such as tebra_search_patients (when no ID is known) or tebra_get_patient_authorizations (authorizations only). No exclusions or alternative routing are given, so usage context is implied rather than stated.

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