Skip to main content
Glama

get_vo2max

Retrieve VO2 Max estimate for running and cycling on a specific date. For today's data, use yesterday as availability may be delayed.

Instructions

Get VO2 Max estimate for a date (running and cycling). Data may not be available for today, use yesterday. For ranges use get_vo2max_range

Input Schema

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

Implementation Reference

  • Handler that calls the Garmin API endpoint to fetch VO2 Max data for a given date. Uses the VO2_MAX_ENDPOINT constant.
    async getVO2Max(date?: string): Promise<unknown> {
      const resolvedDate = date ?? todayString();
      return this.request(`${VO2_MAX_ENDPOINT}/${resolvedDate}/${resolvedDate}`);
    }
  • Input schema for the get_vo2max tool. Requires 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'),
    });
  • Registration of the 'get_vo2max' tool on the MCP server with description and handler that delegates to client.getVO2Max(date).
    export function registerPerformanceTools(server: McpServer, client: GarminClient): void {
      server.registerTool(
        'get_vo2max',
        {
          description:
            'Get VO2 Max estimate for a date (running and cycling). Data may not be available for today, use yesterday. For ranges use get_vo2max_range',
          inputSchema: dateParamSchema.shape,
        },
        async ({ date }) => {
          const data = await client.getVO2Max(date);
          return {
            content: [{ type: 'text' as const, text: JSON.stringify(data, null, 2) }],
          };
        },
      );
  • API endpoint constant for VO2 Max data: /metrics-service/metrics/maxmet/daily
    export const VO2_MAX_ENDPOINT = '/metrics-service/metrics/maxmet/daily';
    export const TRAINING_READINESS_ENDPOINT = '/metrics-service/metrics/trainingreadiness';
  • Registration of the related 'get_vo2max_range' tool that fetches VO2 Max over a date range.
    server.registerTool(
      'get_vo2max_range',
      {
        description:
          'Get VO2 Max data over a date range (day-by-day). Returns array of {date, data} records',
        inputSchema: dateRangeParamSchema.shape,
      },
      async ({ startDate, endDate }) => {
        const data = await client.getVO2MaxRange(startDate, endDate);
        return {
          content: [{ type: 'text' as const, text: JSON.stringify(data, null, 2) }],
        };
      },
    );
Behavior3/5

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

No annotations are present, so the description bears full responsibility for behavioral disclosure. It mentions potential data unavailability for today but does not describe error handling, return format, or whether the operation is read-only. Basic adequacy but lacks depth.

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 sentences, front-loaded with the core action, and no unnecessary words. Efficient and well-structured.

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?

No output schema is provided, and the description does not explain what the tool returns (e.g., a numeric value, units, or object). Given the low complexity, the missing output specification is a noticeable gap.

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?

Input schema covers the single date parameter with pattern and description (100% coverage). The description adds the guidance to use yesterday, which is marginally helpful but does not significantly enhance understanding beyond the schema.

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?

Description clearly states it retrieves VO2 Max estimate for a given date, specifying running and cycling, and distinguishes from the sibling tool get_vo2max_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 advises that data may not be available for today and suggests using yesterday. Also directs users to get_vo2max_range for date ranges, providing clear when-to-use and when-not-to.

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