Skip to main content
Glama
jamesrosing

tebra-mcp-server

by jamesrosing

tebra_create_patient

Creates a patient record in Tebra with required name and date of birth, and supports adding insurance, address, and guarantor details.

Instructions

Create a new patient in Tebra with demographics, address, insurance, and guarantor information.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
firstNameYesPatient first name
lastNameYesPatient last name
dateOfBirthYesDate of birth (ISO 8601, e.g. 1990-01-15)
genderNoOptional gender (Male, Female, Other)
emailNoOptional email address
homePhoneNoOptional home phone number
mobilePhoneNoOptional mobile phone number
address1NoOptional street address line 1
address2NoOptional street address line 2
cityNoOptional city
stateNoOptional state (2-letter abbreviation)
zipCodeNoOptional ZIP code
ssnNoOptional SSN (will be transmitted securely)
referralSourceNoOptional referral source
primaryInsuranceNoOptional primary insurance information
guarantorNoOptional guarantor information
externalIdNoOptional external system ID
Behavior2/5

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

Description only states creation action. No annotation support. Does not disclose side effects, permission requirements, rate limits, or whether patient creation is idempotent. Behavioral traits beyond basic mutation are absent.

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?

Single sentence covering main purpose without extraneous words. Information is front-loaded and efficient.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite schema richness, the description lacks output/return value information (no output schema) and does not address validations, error handling, or behavior for optional fields. Incomplete for a complex create tool with many parameters and nested objects.

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?

Input schema has 100% coverage with descriptions for all 17 parameters, including nested objects. The description does not add extra semantic value beyond listing categories.

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?

Description clearly states verb 'Create' and resource 'patient in Tebra' with scope of data (demographics, address, insurance, etc.). Differentiates from sibling tools like tebra_update_patient or tebra_get_patient.

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

Usage Guidelines2/5

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

No guidance on when to use vs alternatives (e.g., tebra_search_patients for existing patients, tebra_update_patient for modifications). No prerequisites or caveats provided.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/jamesrosing/tebra-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server