Skip to main content
Glama

get_body_composition

Read-only

Retrieve body composition data from Garmin Connect for a single date or a date range by providing a start date and optional end date.

Instructions

Get body composition data for a single date or date range

    Args:
        start_date: Date in YYYY-MM-DD format or start date if end_date provided
        end_date: Optional end date in YYYY-MM-DD format for date range
    

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>"
    },
    "name": "get_body_composition"
  }
}

Input Schema

NameRequiredDescriptionDefault
end_dateNo
start_dateYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/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 and the bar is lower. The description adds only the date/range scoping behavior; it says nothing about whether missing dates return empty results, what timezone dates are interpreted in, or what fields the body composition payload contains.

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?

The core sentence is front-loaded and states purpose and scope in one line. The trailing Python docstring "Args:" block is boilerplate that partially restates the schema, slightly diluting rather than adding to the payload.

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

Completeness3/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 should say what body composition data is returned (weight, body fat, muscle mass, timestamps) and it does not. For a two-parameter read tool this is close to adequate, but the missing return-value and timezone context leaves a gap.

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%, so the description carries the full burden and does supply the YYYY-MM-DD format and the role of end_date as an optional range bound, which is real added meaning. However it omits semantics an agent needs, such as behavior when end_date precedes start_date, timezone handling, and any maximum range limit.

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 composition data") and scopes it precisely to "a single date or date range." It does not differentiate from the sibling write tool add_body_composition or from get_stats_and_body, so an agent must infer read-vs-write on its own.

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 phrase "single date or date range" implicitly tells the agent it can call with start_date alone or with both dates, which is useful context. But there is no explicit when-to-use statement, no exclusions, and no pointer to related tools such as add_body_composition or get_stats_and_body for overlapping data.

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