Skip to main content
Glama
Sign In
garmin-mcp

garmin-mcp

by Sinfjell
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

get_body_battery

Retrieve daily Body Battery summaries over a date range to track charged points, drained points, and highest/lowest energy levels for recovery and stress analysis.

Instructions

Get Body Battery (energy reserve) summary per day over a date range.

start_date and end_date must be "YYYY-MM-DD". Returns a JSON array with one object per day: date, charged (points gained), drained (points lost), highest, and lowest Body Battery level. Per-minute level arrays are stripped; highest/lowest are derived from them before stripping.

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": {
      "start_date": "<start_date>",
      "end_date": "<end_date>"
    },
    "name": "get_body_battery"
  }
}

Input Schema

NameRequiredDescriptionDefault
end_dateYes
start_dateYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations provided, the description carries the full burden and does well: it discloses that per-minute level arrays are stripped and that highest/lowest are derived before stripping, which is meaningful processing behavior an agent would not otherwise know. It stops short of covering permissions, rate limits, or empty-result behavior.

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 purpose sentence is front-loaded, followed by the format constraint and then return shape. No filler; every clause adds information an agent needs.

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?

For a simple two-parameter read tool with an output schema present, the description is nearly complete: it covers the date format and summarizes the return shape. Minor gaps are ordering validation (end before start) and timezone handling.

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 description coverage is 0% and both parameters are bare strings titled 'Start Date'/'End Date', so the description must compensate — and it does by mandating the "YYYY-MM-DD" format and clarifying both are the range bounds. Timezone and inclusive/exclusive semantics remain unspecified.

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?

States a specific verb and resource ('Get Body Battery (energy reserve) summary per day over a date range'), which is unambiguous and clearly distinct from siblings like get_daily_stats or get_sleep. It does not explicitly name a sibling to differentiate against, which keeps it just short of a 5.

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?

The date-range scoping implies when the tool applies, but there is no explicit when-to-use versus alternatives (e.g., get_daily_stats), no stated exclusions, and no preconditions. Usage must be inferred from the description.

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