Skip to main content
Glama

get_spo2

Retrieve blood oxygen saturation (SpO2) data for a given date. Accepts a date in YYYY-MM-DD format.

Instructions

Get blood oxygen saturation (SpO2) data for a specific date. Single date; for ranges use get_spo2_range

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dateNoDate in YYYY-MM-DD format. Defaults to today if not provided

Implementation Reference

  • Registration and handler for the get_spo2 tool. Calls client.getSpO2(date) and returns formatted JSON response.
    server.registerTool(
      'get_spo2',
      {
        description: 'Get blood oxygen saturation (SpO2) data for a specific date. Single date; for ranges use get_spo2_range',
        inputSchema: dateParamSchema.shape,
      },
      async ({ date }) => {
        const data = await client.getSpO2(date);
        return {
          content: [{ type: 'text' as const, text: JSON.stringify(data, null, 2) }],
        };
      },
    );
  • Client method that makes the actual API request to the Garmin SpO2 endpoint. Defaults to today's date if none provided.
    async getSpO2(date?: string): Promise<unknown> {
      const resolvedDate = date ?? todayString();
      return this.request(`${DAILY_SPO2_ENDPOINT}/${resolvedDate}`);
    }
  • Input schema used by get_spo2 tool: accepts an optional date string in YYYY-MM-DD format.
    export const dateParamSchema = z.object({
      date: dateString
        .optional()
        .describe('Date in YYYY-MM-DD format. Defaults to today if not provided'),
    });
  • Tool registered under name 'get_spo2' on the MCP server.
    server.registerTool(
      'get_spo2',
      {
        description: 'Get blood oxygen saturation (SpO2) data for a specific date. Single date; for ranges use get_spo2_range',
        inputSchema: dateParamSchema.shape,
      },
      async ({ date }) => {
        const data = await client.getSpO2(date);
        return {
          content: [{ type: 'text' as const, text: JSON.stringify(data, null, 2) }],
        };
      },
    );
  • API endpoint constant for SpO2 data: /wellness-service/wellness/daily/spo2
    export const DAILY_SPO2_ENDPOINT = '/wellness-service/wellness/daily/spo2';
Behavior3/5

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

No annotations are provided, so the description carries the burden. It discloses the core behavior (get SpO2 for a single date) but does not mention any additional behavioral traits such as default date behavior, authentication requirements, or data format. Adequate but minimal.

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?

The description is two sentences, front-loaded with the main action, and contains no unnecessary words.

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 retrieval tool with one optional parameter and no output schema, the description adequately covers the purpose and usage context. It could be slightly improved by mentioning the default date behavior, but it is largely complete.

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 100%, with the schema already providing a description of the 'date' parameter. The description adds no extra meaning beyond the schema, warranting the baseline score of 3.

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

Purpose5/5

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

The description clearly states the tool retrieves SpO2 data for a specific date, and explicitly distinguishes it from the sibling tool get_spo2_range by noting 'for ranges use get_spo2_range'.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly states that this tool is for a single date and directs to an alternative (get_spo2_range) for date ranges, providing clear context on when to use each.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Nicolasvegam/garmin-connect-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server