Skip to main content
Glama

health

Read-onlyIdempotent

Retrieve Garmin fitness and wellness metrics including heart rate, HRV, SpO2, weight goals, fitness age, VO2 max, and women's cycle data for tracking and analysis.

Instructions

Heart rate, HRV, SpO2, weight, goals, fitness age, VO2 max and women's health. Use discover for exact operation parameters.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "operation": "<operation>",
      "parameters": "<parameters>"
    },
    "name": "health"
  }
}

Input Schema

NameRequiredDescriptionDefault
operationYes
parametersYesExact operation arguments. Use discover(domain, operation) for the schema.

Output Schema

NameRequiredDescriptionDefault
dataYes
errorNo
request_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is covered. The description adds only the discover indirection and says nothing about pagination, units, data freshness, or authentication beyond what the annotations and output schema convey.

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?

Two short sentences with no padding, and the domain list is front-loaded. The cost is that the first sentence is a fragment without a verb, which weakens structure slightly without adding waste.

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 router tool exposing twelve operations behind a discover step, the description is adequate: it tells the agent what data exists and where to get the argument schema, and an output schema is present. It stops short of telling the agent how to pick between operations or how this domain differs from the sibling activity/wellness tools.

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 coverage is 50% and the nested parameters object merely repeats the discover pointer that the schema already contains. The description does add partial meaning by naming data domains that map to several enum values (hrv, spo2, vo2_max_range, weight_goals, menstrual_cycle_*), but it never explains the individual operations.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description enumerates the data domains covered (heart rate, HRV, SpO2, weight, goals, fitness age, VO2 max, women's health), which lets an agent infer this is the health-metrics surface. However, it is a bare noun list with no verb ('retrieves', 'queries') and offers no explicit differentiation from the sibling tools activity, wellness, and profile.

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?

The only guidance is 'Use discover for exact operation parameters', which is a workflow prerequisite rather than a when-to-use rule. There is no statement of when this tool should be chosen over activity, wellness, or profile, and no exclusions or preconditions.

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