Skip to main content
Glama
chrischall

MyAtriumHealth MCP Server

by chrischall
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

mah_get_menu

Read-only

List the features available in a MyAtriumHealth account portal menu to discover what data and tools can be accessed before making further calls.

Instructions

List the features this MyAtriumHealth account exposes (the portal menu). Useful for discovering what is available before calling other tools.

Input Schema

TableJSON 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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.3

TDQS

A3.8/5.0
Behavior3/5

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

The readOnlyHint annotation already establishes this is a safe read, so the description needn't restate safety. It adds useful framing as a capability-discovery call, but says nothing about response shape, its relationship to the 'view' parameter's projection behavior, or how the menu maps to sibling tools.

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, front-loaded with the core purpose and followed by the usage cue. No filler or redundancy.

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?

No output schema exists, but for a zero-required-parameter, read-only discovery tool the description is sufficient to call it correctly. It could say more about what the menu returns or how it relates to the sibling readers, which is the only real gap.

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 is documented in exceptional detail. The description adds nothing about the parameter, so the baseline 3 for schema-carried semantics 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 and resource ('List the features this MyAtriumHealth account exposes') and clarifies the resource with the parenthetical '(the portal menu)'. It reads clearly as a discovery/menu tool rather than a data reader, though it doesn't name a sibling to differentiate against.

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?

'Useful for discovering what is available before calling other tools' gives a clear precondition for use. It lacks explicit when-not guidance or named alternatives, but the ordering advice is actionable.

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