Skip to main content
Glama

get_stats_and_body

Read-only

Retrieve Garmin Connect daily stats and body composition data for a specific date in YYYY-MM-DD format to review health metrics and body measurements.

Instructions

Get stats and body composition data

    Args:
        date: Date in YYYY-MM-DD format
    

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": {
      "date": "<date>"
    },
    "name": "get_stats_and_body"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.5/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds nothing beyond that: it does not say what metrics come back, whether data is per-day or per-record, what happens when no data exists for the date, or how it relates to the narrower stats/body-composition tools.

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

Conciseness3/5

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

The text is short and the purpose sentence is front-loaded, but the residual docstring scaffolding ("Args:" block with a lone parameter restating the schema property) is noise rather than signal. Half the definition is spent on a formatting artifact.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description carries the burden of explaining what is returned, yet it never enumerates which stats or which body-composition fields come back. For a read tool that overlaps three sibling tools, that omission leaves an agent unable to choose confidently.

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 description coverage is 0% — the single `date` property is typed only as a bare string — so the description's "YYYY-MM-DD format" note is genuinely additive and prevents an ambiguous date string. It stops short of clarifying timezone handling or whether the date is interpreted in local or UTC terms.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names two resources (stats and body composition), which is more specific than a tautology, but it gives no clue how it differs from the sibling tools get_stats, get_body_composition, or get_stats_range that appear to cover the same territory. An agent cannot tell whether this is a superset convenience call or something distinct.

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 statement of when to use this tool versus get_stats or get_body_composition, and no prerequisites or exclusions are given. The only guidance is the date argument format, which is parameter-level, not usage-level.

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