Skip to main content
Glama
Garmin Health MCP

Garmin Health MCP

by EmilbMadsen

get_body_battery

Read-only

Retrieve daily Garmin Body Battery charged and drained levels, intraday changes, and event impacts (sleep, activities, stress) with Garmin feedback.

Instructions

Body Battery per day: charged and drained, level over the day, and events that changed it (sleep, activities, stress) with their impact and Garmin's feedback.

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": "get_body_battery"
  }
}

Input Schema

NameRequiredDescriptionDefault
end_dateNoLast date (YYYY-MM-DD), inclusive. Default: today.
start_dateNoFirst date (YYYY-MM-DD), inclusive. Default: 6 days before end_date.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds useful behavioral context about what is reported (per-day charge/drain, event impacts, Garmin's own feedback). It does not mention data-availability caveats, such as the need to have worn the device, or how incomplete days are represented.

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?

A single front-loaded sentence that leads with the resource and then enumerates the returned signals. Every clause carries content, with no filler or restated boilerplate. The mid-sentence line break is cosmetic and does not harm readability.

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?

Because an output schema exists, the description need not describe return shapes, and parameters plus annotations are well documented. It covers what the tool reports and at what granularity (per day). The main omission is a note on data availability or gaps, which matters for a wearable-derived read.

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 100%: both start_date and end_date are typed, optional, and carry their formats plus default-window semantics (today, and six days before end_date). The description adds nothing about the date range, so it neither compensates for nor duplicates the schema. Baseline 3 applies.

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) and enumerates its contents: charged/drained amounts, level over the day, and the events (sleep, activities, stress) with their impact and Garmin's feedback. That gives an agent a clear picture of what the tool returns. It stops short of distinguishing itself from siblings like get_daily_summaries or get_stress, which may surface overlapping signals.

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?

There is no explicit when-to-use guidance, no exclusions, and no pointer to an alternative tool. The agent must infer from the content list that this is the tool for daily energy-level questions rather than stress or sleep queries. The default date window is documented only in the schema, not the description.

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