Skip to main content
Glama
Garmin Health MCP

Garmin Health MCP

by EmilbMadsen

get_weight

Read-only

Retrieve Garmin weigh-ins for a date range, including weight, BMI, body composition, range average, and nearest measurements before and after.

Instructions

Weigh-ins in a date range (weight in grams, BMI and body composition if measured), the range average, and the nearest weigh-in before and after the range.

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": "get_weight"
  }
}

Input Schema

NameRequiredDescriptionDefault
end_dateNoLast date (YYYY-MM-DD), inclusive. Default: today.
start_dateNoFirst date (YYYY-MM-DD), inclusive. Default: 6 days before end_date.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds one genuinely useful behavioral detail — that it also returns the nearest weigh-in just before and after the range — but says nothing about pagination, empty-range behavior, or whether missing body composition fields are omitted or null.

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?

A single tight sentence with no filler, and the most important scope and payload details lead. The parenthetical list of returned fields is dense but earns its space as a summary of the payload.

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 read-only, two-parameter date-range query with an output schema and full annotation coverage, this is close to sufficient — it conveys scope and payload shape. It only falls short on the absence of any usage or alternative guidance.

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 coverage is 100% and both parameters are documented with formats and defaults, so the baseline applies. The description adds only the loose idea of a 'range' without contributing syntax or edge-case meaning (e.g., what an inverted range does) beyond the schema.

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?

The description names the resource (weigh-ins) and enumerates the fields returned — weight in grams, BMI, body composition, range average, plus boundary weigh-ins. It's specific enough to distinguish from get_weight_goals, but it never uses an explicit action verb like 'retrieve' and doesn't contrast itself with the goals sibling.

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 when-to-use guidance: no statement of prerequisites, no alternative to reach for when the agent wants goals rather than measurements, and no exclusions. The defaults (today, 6 days back) come only from the schema, not the description, so an agent gets no routing signal from the prose.

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