garmin-mcp-server

by JohanBellander

Overview Schema Source Related Servers Discussions Admin

Python

Local

get_vo2max

Retrieve estimated VO2 Max for running and cycling for a specific date in YYYY-MM-DD format.

Instructions

Get VO2 Max / max metrics data for a date (YYYY-MM-DD). Returns estimated VO2 Max for running and cycling.

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_vo2max"
  }
}

Input Schema

Name	Required	Description	Default
`date`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 30, 2026

TDQS

A3.8/5.0

Behavior3/5

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

With no annotations, the description carries the behavioral burden. It discloses that values are estimates and that it covers running and cycling, which is useful. It does not mention missing-data behavior, units, or any caveats beyond 'estimated'.

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 with no filler; the action, format, and output contents are front-loaded. Every clause earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single-parameter getter with an output schema, this description covers invocation format and expected content. Nothing needed to make the call is missing; return-value details are left to the output schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, but the description supplies the required date format '(YYYY-MM-DD)', which is exactly the kind of information the schema omits. For the sole parameter, this is sufficient semantic guidance.

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, resource, and time scope: 'Get VO2 Max / max metrics data for a date'. The second sentence narrows the output to estimated running and cycling VO2 Max, making the resource clear. It does not explicitly contrast with the many sibling metric tools, but VO2 Max is unambiguous among them.

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

Usage Guidelines3/5

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

The intended use is implied: call it when you need VO2 Max for a specific date. No exclusions or alternative tool recommendations are provided, and with many sibling tools some routing guidance would have helped.

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