Skip to main content
Glama
jamesrosing

tebra-mcp-server

by jamesrosing
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Get All Patients

tebra_get_all_patients
Read-only

Retrieves patient records in paginated batches, returning a page with a continuation key to fetch the next set. Optionally filter by active status, practice, or request extra fields.

Instructions

Get all patients in bulk with pagination. Returns a page of patients and a continuation key for the next page. Use startKey from the previous response to get the next batch. By default each row is a roster entry (patientId, firstName, lastName, dateOfBirth, mrn, active); pass fields to request contact, insurance, or practice columns.

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.
isActiveNoOptional filter: true for active patients only, false for inactive only (applied client-side; the returned count reflects the filtered page)
startKeyNoContinuation key from previous response (omit for first page)
batchSizeNoNumber of patients per page (default 200, max 1000)
practiceIdNoOptional practice ID filter

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields 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"
+}
    • changedInput schema / properties / isActive / description
      Previous value: -"Optional filter: true for active patients only, false for inactive only"New value: +"Optional filter: true for active patients only, false for inactive only (applied client-side; the returned count reflects the filtered page)"
    • addedInput schema / properties / practiceId
      Added value: +{
+  "description": "Optional practice ID filter",
+  "type": "string"
+}
  2. First observedv0.2.5

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already mark this as read-only, and the description adds meaningful behavior: it returns a page plus a continuation key, requires startKey from the prior response, and documents the default roster entry field set. This goes beyond the annotations and helps the agent predict the response shape even without an output schema.

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 tight sentences front-load the core purpose, then explain pagination, and then describe the default field set and how to extend it. There is no filler, repetition, or content that belongs only in the schema.

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 bulk-read tool with full parameter documentation, readOnlyHint, and no output schema, this description is complete. It covers the return shape, pagination mechanism, default fields, and how to request additional fields, leaving no critical gap for an agent deciding to call it.

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%, so all five parameters are already documented with their own descriptions. The description reinforces startKey and fields usage but does not add significant new semantic detail beyond what the schema provides. Baseline 3 is appropriate.

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 opens with 'Get all patients in bulk with pagination,' which gives a specific verb, resource, and scope. It clearly distinguishes this from sibling tools like tebra_get_patient and tebra_search_patients by emphasizing bulk retrieval of all patients rather than a single record or a filtered search.

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 gives clear operational context: use it for bulk patient retrieval, follow pagination with startKey, and pass fields for additional columns. It does not explicitly name alternatives or state when not to use it, but the bulk-vs-single distinction is strongly implied by the wording.

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