Skip to main content
Glama
MyAtriumHealth MCP Server

MyAtriumHealth MCP Server

by chrischall

mah_list_care_team

Read-only

List care team providers with names, specialties, and relationships from this organization and linked outside organizations.

Instructions

List care team providers — name, specialty and relationship — from this organization and from linked outside organizations.

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

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

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds one genuinely useful behavioral fact beyond the annotations: results span both the organization and linked outside organizations, which is a cross-boundary data scope an agent should know. It says nothing about auth requirements, rate limits, or result size.

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?

One sentence, front-loaded with the verb and resource, with the scope qualifier appended. Zero filler and nothing redundant with structured fields.

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 list tool with no output schema, the description usefully names the returned fields (name, specialty, relationship) and the data scope, and the only parameter is fully documented in the schema. An agent has enough to call it correctly, though nothing indicates ordering, pagination, or empty-result behavior.

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 carries a very detailed enum description, so the schema does the heavy lifting. The tool description mentions the parameter not at all, adding no meaning beyond the schema. Baseline 3 is appropriate.

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 (care team providers), and even enumerates the fields returned: name, specialty and relationship. It also scopes the source as this organization plus linked outside organizations. It does not explicitly differentiate itself from the many sibling list_* readers, though the resource is unique enough to be distinguishable.

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 guidance on when to use this tool versus alternatives, nor any prerequisites or exclusions. Usage is only implied by the resource name, which is a weak signal given 20+ sibling readers. The description would need an explicit trigger condition to score higher.

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