Skip to main content
Glama
Garmin Health MCP

Garmin Health MCP

by EmilbMadsen

get_spo2

Read-only

Retrieve blood oxygen (SpO2) data for a single day, including day and sleep averages, lowest and latest readings, 7-day average, and hourly averages.

Instructions

Blood oxygen (SpO2) for one day: day and sleep averages, lowest, latest, 7-day average, and hourly averages.

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": "get_spo2"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNoDate as YYYY-MM-DD in the user's time zone. Leave empty for today.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/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 the useful detail that results include both sleep-window and hourly breakdowns plus a rolling 7-day average, which is more than a per-day tool would suggest. It says nothing about permissions, data availability, or freshness, and the returned structure is largely covered by the existing output schema.

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?

A single front-loaded sentence with no filler; the resource and its returned metrics come first. The inline metric list is dense but each item earns its place by telling the agent what data is available. No closing boilerplate or redundant restatement.

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 simple, single-optional-parameter read tool with full schema coverage, read-only annotations, and an output schema, the description covers what data comes back and the one-day scope. The remaining gap is the absence of any routing guidance relative to the many sibling health-metric 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?

With a single parameter at 100% schema description coverage, the schema already explains the date format (YYYY-MM-DD, user's time zone) and the 'leave empty for today' default. The description contributes only the vague 'for one day' framing, adding no format or edge-case meaning beyond the schema, so baseline 3 applies.

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?

The description names a specific resource (blood oxygen / SpO2) and enumerates exactly what is returned: day and sleep averages, lowest, latest, 7-day average, and hourly averages. That is far more specific than the bare name, though it never distinguishes this from siblings like get_heart_rate or get_sleep, which also report per-day health metrics.

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 explicit when-to-use guidance, and no alternative is named. The only scoping signal is the phrase 'for one day', which the agent must infer means a single-date lookup rather than a range query. Nothing tells the agent when another tool (e.g. get_sleep) would be the better choice for related data.

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