Skip to main content
Glama
chrischall

MyAtriumHealth MCP Server

by chrischall
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

mah_list_test_results

Read-only

List lab and imaging results with test name, abnormal flag, date, ordering provider, and comments; flags partial history.

Instructions

List lab and imaging results: name, abnormal flag, date, ordering provider and any provider comment. Individual result values load on the detail page and are not in this list. Compact output is { items, complete, note }: complete is false when the portal loaded only part of the history.

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.9/5.0
Behavior4/5

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

With readOnlyHint already covering the safety profile, the description adds real behavioral context: it declares the absence of individual values, describes the compact payload shape ({ items, complete, note }), and explains the semantics of complete=false as a partial-history signal. This partial-data warning is exactly the kind of disclosure annotations cannot carry.

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?

Three sentences, each earning its place: field list first, exclusion second, output shape third. No padding or restatement of the tool name. Slightly dense prose but well front-loaded.

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?

There is no output schema, so the description correctly compensates by naming the fields and the compact envelope plus the meaning of 'complete'. The main residual gap is that the 'detail page' mechanism for individual values is referenced but not mapped to any sibling tool, leaving the agent to search.

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' enum parameter is documented in exhaustive detail in the schema itself. The description adds nothing about the view parameter, so baseline 3 applies – the schema does all the semantic work here.

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?

States a specific verb and resource ('List lab and imaging results') and enumerates the returned fields (name, abnormal flag, date, ordering provider, provider comment), which cleanly separates it from the other mah_list_* readers. An agent can identify the tool without opening the schema.

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?

Implicitly guides usage by scoping what is NOT returned ('Individual result values load on the detail page and are not in this list'), which prevents misdirected calls, but it never names a sibling or gives an explicit when-to-use condition or prerequisite. Adequate context, no routing to alternatives.

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