Skip to main content
Glama

garmin_body_battery

Read-onlyIdempotent

Retrieve per-day Garmin energy estimates with charged and drained levels, min/max values, and events such as sleep, activities, and naps; optionally include an intraday timeline for up to 31 days.

Instructions

Per-day Body Battery (Garmin's 0-100 energy estimate): charged, drained, min/max, events that changed it (sleep, activities, naps) and Garmin's feedback. Optional intraday timeline. Range up to 31 days, default last 3.

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

Input Schema

NameRequiredDescriptionDefault
daysNoNumber of days ending at end_date, used when start_date is omitted.
end_dateNoLast day, YYYY-MM-DD. Default: today.
start_dateNoFirst day, YYYY-MM-DD in the user's local calendar. Default: computed from end_date and days.
include_timelineNoInclude the intraday level series (adds roughly 1-3 KB per day).

Output Schema

NameRequiredDescriptionDefault
toYes
daysYes
fromYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, and openWorld, so the safety profile is covered. The description adds genuinely new behavioral facts beyond them: the 31-day range ceiling and the 3-day default window, which shape how calls behave. It does not mention payload cost of the timeline (that lives in the schema) or any rate limiting, keeping this at solid-but-not-rich.

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?

Three short sentences, front-loaded with the resource and its payload, then the optional flag, then the range constraint. No filler, no restatement of the tool name, and the most decision-relevant facts come first.

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?

An output schema exists, so return-value documentation is not required, and the range/default details plus the timeline caveat are enough to call the tool correctly. The only gap is selection guidance relative to adjacent Garmin tools for daily aggregates or trends.

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 100%, so the baseline is 3; the description earns a bump by stating the 31-day maximum, which the schema does not encode, and by flagging the intraday timeline as optional. It still leaves the interaction between start_date and days to the schema rather than clarifying precedence.

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 (per-day Body Battery) and enumerates its content precisely: charged/drained, min/max, events (sleep, activities, naps), and Garmin's feedback, plus an optional intraday series. The resource is distinctive enough against siblings like garmin_heart_rate or garmin_sleep, though it never explicitly contrasts itself with garmin_daily_summary or garmin_trends.

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?

Usage context is implied rather than stated: the agent learns the default window is the last 3 days and the hard cap is 31 days, and that the timeline is optional. There is no explicit when-to-use, when-not-to-use, or pointer to an alternative sibling for coarser summaries or longer-horizon trends.

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