garmin-connect-api

List weigh-ins

list_weigh_ins

Read-onlyIdempotent

Fetch all weigh-ins from a start date (end defaults to start), oldest first, with body composition and the sample_pk for deletion. Includes every reading on days with multiple entries.

Instructions

List every weigh-in from start to end (end defaults to start), oldest first, with body composition and the sample_pk that delete_weigh_in takes.

Includes every reading on days with more than one. For weight or body fat as one value a day with an average and the change, use get_trend with metric weight or body_fat; get_day_summary gives the day's last weigh-in.

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

Input Schema

Name	Required	Description	Default
`end`	No	Last day, inclusive.
`start`	Yes	First day, inclusive.

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.0Oct 20, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations cover read-only/idempotent safety, but the description adds real behavioral context: it includes every reading on multi-reading days, returns oldest-first, and surfaces body composition plus a delete-compatible sample_pk. It stops short of describing pagination or date-range bounds, which is a minor 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-loaded with the core behavior, then the sibling routing. Every clause is informative, though the three-way comparison against get_trend and get_day_summary makes it slightly dense.

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

Completeness5/5

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

With an output schema present, return values need no explanation, and the description still covers ordering, deduplication of multi-reading days, the end default, and alternative tools. Nothing an agent needs to call it correctly is missing.

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 already 100%, so baseline is 3. The description adds meaning beyond the schema by stating that end defaults to start, a defaulting behavior the schema does not encode.

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?

States a specific verb and resource ('List every weigh-in') with an explicit range and ordering ('from start to end, oldest first'). It clearly distinguishes itself from sibling read tools by naming get_trend and get_day_summary as alternatives for different views.

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?

Explicitly routes the agent: use get_trend for a single daily value with average/change, use get_day_summary for the day's last weigh-in, and use this tool for every reading. It also tells the agent the returned sample_pk is what delete_weigh_in consumes.

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