Skip to main content
Glama
Sign In
Garmin MCP Server

Garmin MCP Server

by JJRPF
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_respiration_data

Retrieve detailed respiration time-series data for a specific date. Returns interval-level measurements to analyze breathing patterns throughout the day.

Instructions

Get full respiration time-series data

Note: This returns detailed interval data (~20KB). For a compact summary, use get_respiration_summary().

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

Input Schema

NameRequiredDescriptionDefault
dateYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior3/5

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

No annotations are provided (no readOnlyHint or destructiveHint), so the description carries the burden. It mentions the response size (~20KB) and implies a read-only 'Get' operation, but it doesn't explicitly state that there are no side effects or that the request may be large/slow beyond the size note.

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 short and well-structured: a clear purpose, a note about data size, an alternative reference, and an Args section. Every sentence adds value and there is no redundant content.

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?

Given the single parameter and no output schema shown, the description covers the key context: what data is returned, its approximate size, the alternative for summaries, and the expected date format. It's sufficient for an agent to call it correctly, though a brief note on the response structure would fully round it out.

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?

The input schema provides only 'date' with type string and no description (0% schema coverage). The description compensates by specifying the format 'YYYY-MM-DD', which adds meaning beyond the schema. However, it doesn't explain what date range or timezone assumptions apply, so a small gap remains.

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 states a specific verb ('Get') and resource ('full respiration time-series data'). It explicitly distinguishes itself from the sibling tool get_respiration_summary, so an agent can identify which tool to use without opening other schemas.

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?

The description explicitly names the alternative get_respiration_summary() and gives the condition for using it ('For a compact summary'). It also notes the data size (~20KB), providing clear guidance on when to choose this tool versus the summary.

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