Skip to main content
Glama

getBodyBattery

Read-only

Retrieve up to 14 days of Body Battery readings, charge/drain events, and Garmin feedback to identify why energy levels rose or fell.

Instructions

Body Battery for up to 14 days, yyyy-MM-dd: for each day how much it charged and drained, its readings through the day as [timestamp, level] pairs, and the events that changed it (sleep, activities, stress, naps) with their start, duration and impact, and Garmin's feedback. Use it to see why Body Battery went up or down. For one number per day with steps and stress use getDailySummary; for the change of one activity, listActivities.

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": {
      "fromDate": "<fromDate>",
      "toDate": "<toDate>"
    },
    "name": "getBodyBattery"
  }
}

Input Schema

NameRequiredDescriptionDefault
toDateYesTo date yyyy-MM-dd
fromDateYesFrom date yyyy-MM-dd

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.13.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations only declare readOnlyHint and openWorldHint; the description adds real behavioral value by disclosing the response shape (charge/drain totals, intraday readings, event start/duration/impact, Garmin feedback) and the 14-day window. It stops short of stating what happens if the range exceeds 14 days or how large a payload to expect, which is the main remaining gap.

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?

Front-loads the resource and range, then the return contents, then the alternatives; nothing is padding. The middle sentence is long and list-like, but every clause describes a distinct part of the response rather than repeating structured fields.

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?

There is no output schema, so the description must carry the return-value burden, and it does so in detail. Minor omissions remain around out-of-range behavior and timezone/date interpretation, but an agent has enough to call it correctly.

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% and already documents fromDate/toDate as yyyy-MM-dd, so the baseline is 3. The description still adds a constraint not in the schema — that the span is capped at 14 days — which meaningfully informs how the agent should set the range.

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?

Names a specific resource (Body Battery) with a concrete scope (up to 14 days) and enumerates the returned content: per-day charge/drain, [timestamp, level] readings, and the events that changed it. It explicitly distinguishes itself from getDailySummary and listActivities, so an agent can pick it without opening a schema.

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?

Gives an explicit use case ("see why Body Battery went up or down") plus two named alternatives with the conditions that select them: getDailySummary for one number per day with steps and stress, listActivities for a single activity's change. When-to-use, when-not-to-use, and routing are all present.

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