Garmin MCP for macOS

Overview Schema Source Related Servers Discussions Admin

garmin_api_weight_all

Read-only

Retrieves all raw weight measurements from Garmin Connect for a date range, defaulting to 7 days and limited to 31 days, so you can inspect unnormalized weight data.

Instructions

All weight measurements from the weight/all endpoint. Raw JSON fields are not normalized. Date ranges default to 7 days and allow at most 31 days (activity search uses pagination).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "garmin_api_weight_all"
  }
}

Input Schema

Name	Required	Description	Default
`end_date`	No
`start_date`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Oct 26, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Beyond the readOnly/openWorld annotations, it discloses two genuinely useful behaviors: fields are not normalized (raw endpoint shapes) and ranges are capped at 31 days with a 7-day default. The closing pagination remark appears to describe activity search rather than this tool, which muddies rather than clarifies.

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?

Three short sentences front-load the outcome and the normalization caveat before the limits. The trailing 'activity search uses pagination' clause is a non-sequitur for a weight tool and does not earn its place.

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?

Return values need not be explained because an output schema exists, and the description appropriately flags the un-normalized payload shape. The one real gap for a two-date tool is the missing date format/ramge-inclusivity detail.

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 has to carry parameter meaning, and it does add the 7-day default and 31-day ceiling that the schema omits. It still never states the expected date format (e.g. YYYY-MM-DD) or whether the range is inclusive, leaving ambiguity for both parameters.

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+resource ('All weight measurements') and names the underlying endpoint, so an agent knows exactly what is returned. It does not explicitly contrast with the sibling garmin_api_weight_range, which is the closest alternative, so it falls short of full sibling differentiation.

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 description supplies concrete usage constraints — default 7-day range and a 31-day maximum — which implicitly tells the agent how far to reach with this call. However, it never says when to prefer this over garmin_api_weight_range or over paginated alternatives, so the routing guidance is only implied.

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