Skip to main content
Glama
MyAtriumHealth MCP Server

MyAtriumHealth MCP Server

by chrischall

mah_sign_in

Destructive

Signs in to MyAtriumHealth server-side and reports available verification channels for multi-factor authentication when the portal requests a code.

Instructions

Sign in to MyAtriumHealth server-side. If the portal requires a verification code, this reports the available channels — ask the user which they want.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.3

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, openWorldHint=true, and destructiveHint=true, so the agent knows this mutates external state. The description adds real behavioral context — that sign-in may return verification channels rather than completing — but it omits what happens on failure, whether it overwrites an existing session, and where credentials come from.

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 tight sentences with the core action front-loaded and the conditional branch second. No filler, no restatement of the name or title.

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 zero-parameter, no-output-schema auth tool, the description covers the happy path and the verification branch but leaves a notable hole: with no inputs, how authentication credentials or session target are supplied is never addressed, and the relationship to the other auth-flow siblings is undefined.

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?

The tool takes zero parameters, so per the baseline rule this scores 4. There is nothing for the description to disambiguate, though the absence of any input also means the credential/session mechanics are unexplained.

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+resource ("Sign in to MyAtriumHealth") and adds the scope qualifier "server-side," which tells the agent this establishes a server-side session rather than doing something client-local. It is distinguishable from the list/get siblings, though it never names mah_auth_status or the verify_code siblings to sharpen the boundary.

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 second sentence gives clear conditional guidance for the verification-code branch ("ask the user which they want"), which is genuinely useful routing. However, it never says when to call this versus mah_auth_status, mah_send_verification_code, or mah_verify_code, so the primary when-to-use decision is left to inference.

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