garmin-mcp-server

by JohanBellander

Overview Schema Source Related Servers Discussions Admin

Python

Local

get_respiration

Retrieve respiration data for a specific date, showing breathing rate measurements throughout the day.

Instructions

Get respiration/breathing rate data for a date (YYYY-MM-DD). Returns breathing rate throughout the day.

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

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?

No annotations are provided, so the description carries the burden of behavioral disclosure. It does indicate a read operation returning data across the day, which is useful. However, it does not mention units, granularity, timezone behavior, 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two short sentences with no filler. The key action and date format are front-loaded, and the return behavior is stated in the second sentence. Every word earns its place.

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?

This is a low-complexity tool with one required parameter and an output schema. The description covers the purpose, the date format, and the general nature of the result. It is nearly complete for invocation, though it lacks usage guidance and edge-case behavior, which are minor for this simple getter.

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 description coverage is 0%, but there is only one parameter and the description adds the explicit 'YYYY-MM-DD' format. This meaningfully compensates for the schema's lack of description, though it does not add much beyond the format and the semantic notion of 'a date'.

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 uses a specific verb ('Get') and resource ('respiration/breathing rate data'), and adds the date scope and output behavior ('Returns breathing rate throughout the day'). This clearly distinguishes it from sibling tools that target other metrics such as heart rate, SpO2, or stress.

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?

The description explains what the tool does but provides no guidance on when to prefer it over alternatives, nor any exclusions or prerequisites. An agent can infer it is for daily respiration data, but the description does not explicitly help with tool selection.

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