MCP server for reviewed TBC Insurance health-account workflows
TBC Insurance MCP has 17 tools with consistent naming (verb_noun pattern: list_*, get_*, book_*) and descriptions present for all tools. However, descriptions are brief (avg ~60 chars, well below the 194-char baseline for A+ tools) and lack context on WHEN to use each tool or dependencies between them. Input schemas are properly typed with JSON Schema, but parameter descriptions are minimal and lack format/constraint guidance. Output schemas are not documented in the source. Error handling is not visible in the tool definitions. The appointment booking workflow (tools 1-5) shows good composition and chaining (service → location → clinician → slot → book), but the health policy/claims workflow (tools 6-17) lacks clear sequencing guidance.
Book an exact appointment slot through the shared single-use review boundary
Retrieve detailed information about a specific medical claim
Retrieve minimized health-account information used for care and reimbursement
Retrieve detailed state of one reimbursement or guarantee-of-payment request
Translate current availability into complete intervals within a selected date window
Translate date-specific clinicians, checking their selected branch
Descriptions are too brief (avg ~60 chars vs 194-char baseline). Most lack context on WHEN to use the tool, prerequisites, or dependencies. E.g., 'List member-visible health policies' does not explain that this must be called before list_coverage_benefits or list_medical_claims.
Parameter descriptions lack format/constraint guidance. E.g., 'policy_id' is described as 'Exact opaque policy identifier' but does not explain format, length, or how to obtain it. Date parameters (from_date, to_date) lack validation rules (e.g., 'must be YYYY-MM-DD and within 31 days').
Inferred effective spec: <=2025-11-25.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 49 | <=2025-11-25 | v2 |
Retrieve the current TBC appointment-service catalog
List health care items or service categories covered by a policy
List persons entitled to benefits under health policies
List member-visible health policies with direct identifiers minimized
List payment records for medical care already received
List numbered referrals for provider services
List reimbursement or guarantee-of-payment requests tracked by TBC
List contracted health care organizations in TBC's provider network
Translate the current appointment branch catalog into provider locations
List provider services that can be selected for a referral request
List cities available in TBC's health-service search
Output schemas are not documented in the source code. LLMs cannot plan downstream tool calls or extract required fields (e.g., policy_id from list_health_policies to pass to list_coverage_benefits) without knowing the response structure.
Error handling is not visible in tool definitions. No guidance on retryability, user-fixable errors, or recovery steps. E.g., if book_appointment fails due to slot unavailability, the LLM has no direction to retry list_appointment_slots.
Tool composition lacks explicit sequencing. The health policy workflow (tools 6-17) does not document that list_health_policies must precede list_coverage_benefits, or that get_claim_detail requires a claim_id from list_medical_claims. This forces LLMs to infer dependencies.