Garmin MCP for macOS

Overview Schema Source Related Servers Discussions Admin

garmin_api_body_battery

Read-only

Retrieve Garmin Body Battery readings for a date range and optionally group them into intervals, with a default 7-day range and a 31-day maximum.

Instructions

Body Battery readings and optional interval grouping using chunks. Raw JSON fields are not normalized. Date ranges default to 7 days and allow at most 31 days (activity search uses pagination).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "garmin_api_body_battery"
  }
}

Input Schema

Name	Required	Description	Default
`chunks`	No
`end_date`	No
`start_date`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Oct 26, 2026

TDQS

A3.6/5.0

Behavior4/5

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

Annotations already establish the safe-read profile, and the description adds real value on top: outputs are raw, un-normalized JSON, date ranges default to 7 days, are capped at 31, and this endpoint is not paginated. That last point is exactly the kind of behavioral detail an agent needs to avoid assuming pagination support.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

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

Three tight sentences with the resource and the key constraints front-loaded; nothing is redundant. The trailing parenthetical about activity search pagination is slightly cryptic out of context but still earns its place as a contrast.

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?

An output schema exists, so return values are covered, and the safety profile comes from annotations. What remains missing for correct invocation is date format and the semantics/units of `chunks`, which leaves the definition adequate but incomplete for a tool whose parameters are otherwise undocumented.

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 0%, so the description carries the burden and only partially meets it. It explains the date range defaults and cap, and gestures at `chunks` meaning interval grouping, but never specifies the date string format, what units `chunks` takes, or whether the date bounds are inclusive.

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?

The description names a specific resource (Body Battery readings) and an action (retrieving, with optional interval grouping via `chunks`). It does not, however, distinguish this tool from the sibling `garmin_body_battery`, which appears to cover the same resource under a different prefix.

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?

It gives useful operating constraints (7-day default, 31-day maximum) and hints that activity search uses pagination instead, but never says explicitly when an agent should pick this tool over `garmin_body_battery` or any other sibling. Usage is implied by the constraints rather than stated.

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