Skip to main content
Glama
MyAtriumHealth MCP Server

MyAtriumHealth MCP Server

by chrischall

mah_list_test_results

Read-only

List lab and imaging test results—name, abnormal flag, date, ordering provider, and comments—and flag when only part of the history is available.

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.

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

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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.3

TDQS

A4.2/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 genuinely non-obvious behavioral detail: the returned item fields, the compact response shape { items, complete, note }, and the fact that complete=false signals a partially loaded history. It omits auth/session requirements (e.g. dependence on an active patient), which keeps it short of a 5.

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?

Three tight sentences: what it lists and its fields, the notable exclusion, then the response envelope contract. Everything is front-loaded and no sentence is filler or a restatement of the name.

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?

With no output schema, the description carries the return-value burden and does so for the list shape, compact envelope, and the partial-history signal; annotations cover safety semantics. Remaining gaps are secondary details such as authentication state or ordering/limits, which are not blocking for a read-only list.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, and the single 'view' enum is documented at length in the schema, so the baseline would be 3. The description goes slightly beyond by spelling out what the compact view concretely yields for this reader ({ items, complete, note }), which the schema's generic per-server list does not enumerate for this tool.

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 exactly what each item contains (name, abnormal flag, date, ordering provider, provider comment). It also draws a scope boundary the agent would otherwise not know: individual result values live on a detail page and are absent here. No sibling tool covers this resource, so the agent can identify it immediately.

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?

There is no explicit when-to-use or when-not-to-use guidance, and no sibling is named as an alternative. The one routing hint ('individual result values load on the detail page') tells the agent where values it needs are not, but does not name a tool or state a selection condition. Usage is implied rather than specified.

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