Skip to main content
Glama

get_spo2_data

Read-only

Retrieve SpO2 (blood oxygen) data for a specified date from Garmin Connect to review daily oxygen saturation levels.

Instructions

Get SpO2 (blood oxygen) data

    Args:
        date: Date in YYYY-MM-DD format
    

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": {
      "date": "<date>"
    },
    "name": "get_spo2_data"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered externally. The description adds nothing behavioral beyond that — no indication of return granularity (intraday samples vs daily aggregate), timezone handling, or what happens when no data exists for the date.

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?

Very short and front-loaded: the purpose sentence comes first, the format detail second. The docstring-style 'Args:' block is slightly mechanical but costs almost nothing in length.

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 simple one-parameter read tool with annotations and no output schema, the description is minimally adequate: it names the metric and the date format. It is missing the things an agent would still have to guess at — granularity of the returned data and timezone/empty-day 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 0%, so the schema only says the field is a string named 'date'. The description compensates partially by specifying the YYYY-MM-DD format, which is real added meaning. It does not clarify whether this is a calendar day in local time or UTC, nor whether it returns a full day of readings.

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 and resource ('Get SpO2 data') and helpfully glosses the acronym as blood oxygen, which distinguishes it from the many other metric-fetching siblings such as get_hrv_data or get_respiration_data. It stops short of explicitly routing between those siblings, so it is clear but not fully differentiated.

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 when-to-use guidance, no prerequisites, and no mention of alternatives or when this metric is not appropriate. The only usage signal is the implied one from the tool name and required date argument.

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