Skip to main content
Glama
MyAtriumHealth MCP Server

MyAtriumHealth MCP Server

by chrischall

mah_list_billing_accounts

Read-only

Lists billing accounts with balances due, grouped as outstanding, zero-balance, or guarantor-authorized, and returns amounts as displayed.

Instructions

List billing accounts with balance due, grouped as outstanding, zero-balance or guarantor-authorized. Amounts are returned as displayed (formatted strings).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "mah_list_billing_accounts"
  }
}

Input Schema

NameRequiredDescriptionDefault
viewNoResponse shape: "compact" (default) drops fields the response already carries elsewhere; "full" returns every field this server understands. compact strips image/avatar URLs from every response, and on the readers with a projection derived from a captured payload (mah_list_allergies, mah_list_health_issues, mah_list_immunizations, mah_list_medications, mah_list_care_team, mah_list_goals, mah_list_test_results, mah_list_past_visits, mah_list_insurance, mah_list_messages) also reduces each record to its clinically meaningful fields; "full" returns MyAtriumHealth's payload untouched. Every other reader gets the URL strip only, rather than a field list nobody verified. "brief" answers one text line per item: <account> — <ISO due date or "no date"> — <amount> due, for accounts with a balance only, after a "-- patient: <name>" note line naming whose chart was read.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.4.1
    • changedInput schema / properties / view / description
      Previous value: -"Response shape: \"compact\" (default) drops fields the response already carries elsewhere; \"full\" returns every field this server understands. compact strips image/avatar URLs from every response, and on the readers with a projection derived from a captured payload (mah_list_allergies, mah_list_health_issues, mah_list_immunizations, mah_list_medications, mah_list_care_team, mah_list_goals, mah_list_test_results, mah_list_past_visits, mah_list_insurance, mah_list_messages) also reduces each record to its clinically meaningful fields; \"full\" returns MyAtriumHealth's payload untouched. Every other reader gets the URL strip only, rather than a field list nobody verified."New value: +"Response shape: \"compact\" (default) drops fields the response already carries elsewhere; \"full\" returns every field this server understands. compact strips image/avatar URLs from every response, and on the readers with a projection derived from a captured payload (mah_list_allergies, mah_list_health_issues, mah_list_immunizations, mah_list_medications, mah_list_care_team, mah_list_goals, mah_list_test_results, mah_list_past_visits, mah_list_insurance, mah_list_messages) also reduces each record to its clinically meaningful fields; \"full\" returns MyAtriumHealth's payload untouched. Every other reader gets the URL strip only, rather than a field list nobody verified. \"brief\" answers one text line per item: <account> — <ISO due date or \"no date\"> — <amount> due, for accounts with a balance only, after a \"-- patient: <name>\" note line naming whose chart was read."
    • changedInput schema / properties / view / enum
      Previous value: -[
      -  "compact",
      -  "full"
      -]New value: +[
      +  "compact",
      +  "full",
      +  "brief"
      +]
  2. Changed1 schema field changedv1.3.7
    • removedInput schema / properties / raw
      Removed value: -{
      -  "default": false,
      -  "description": "Return the raw page HTML instead of parsed accounts, for debugging.",
      -  "type": "boolean"
      -}
  3. First observedv1.3.3

TDQS

A3.6/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, so safety is covered. The description adds real value beyond them: it discloses the three grouping buckets and, importantly, that amounts are formatted display strings (implying they should not be summed or parsed blindly). It does not mention pagination or whether results are scoped to the active patient.

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?

Two short sentences with zero filler; the resource and grouping are front-loaded and the formatted-string caveat follows. Every clause carries information an agent needs.

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, zero-required-parameter list tool with no output schema, the description is nearly complete: it explains the categorization and the amount format. The remaining gap is that it never states whose accounts are returned (the active patient) or whether the list is bounded.

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% and the single 'view' parameter has a long enum description covering compact/full/brief. The tool description adds nothing about the view parameter, so the baseline of 3 applies — the schema does all the work.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('List billing accounts') plus the grouping semantics (outstanding, zero-balance, guarantor-authorized). No sibling tool covers billing, so differentiation is implicit rather than stated, which keeps it just short of a 5.

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?

There is no when-to-use guidance and no named alternative or exclusion — the agent is not told whether to prefer this over mah_get_patient_context or mah_get_health_summary for financial questions, nor that an active patient must be set. Usage is only inferable from the tool name.

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