Skip to main content
Glama
MyAtriumHealth MCP Server

MyAtriumHealth MCP Server

by chrischall

mah_list_upcoming_visits

Read-only

Lists upcoming and in-progress MyAtriumHealth appointments so you can confirm what's next and track visits already underway.

Instructions

List upcoming and in-progress MyAtriumHealth appointments.

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_upcoming_visits"
  }
}

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: <visit type> — <ISO date or "no date"> — <in progress|upcoming>, after a "-- patient: <name>" note line naming whose chart was read.
timeZoneNoIANA time zone used to bucket appointments.America/New_York

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: <visit type> — <ISO date or \"no date\"> — <in progress|upcoming>, 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. First observedv1.3.3

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint and openWorldHint, so safety is covered. The description adds the useful content-scope detail that in-progress appointments are included, but says nothing about ordering, result volume, or pagination behavior for a list tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with zero filler. Its terseness is the main cost, but this dimension rewards structure and economy, and nothing here is wasted.

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

Completeness3/5

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

For a no-required-param read-only list with full schema coverage and no output schema, the description is minimally sufficient. It does not cover ordering, result limits, or whether multiple patient charts can be in scope, which would matter when interpreting a list of appointments.

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 coverage is 100% and the 'view' enum description is unusually thorough, including the 'brief' line format. The description itself adds no parameter meaning beyond what the schema already provides, so the baseline 3 applies.

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 (List) and resource (MyAtriumHealth appointments) and scopes it to upcoming and in-progress, which implicitly separates it from the sibling mah_list_past_visits. It stops short of naming that sibling explicitly, so differentiation requires the agent to infer it from the scope words.

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 'upcoming and in-progress' qualifier implies when to reach for this over mah_list_past_visits, but there is no explicit when-to-use/when-not or named alternative. Adequate but leaves routing to inference.

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