Skip to main content
Glama
Garmin Health MCP

Garmin Health MCP

by EmilbMadsen

get_weight_goals

Read-only

Retrieve weight goals active during a date range to track target weight progress and goal changes over time.

Instructions

Weight goals in effect during a date 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_goals"
  }
}

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

C2.9/5.0
Behavior2/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 nothing beyond that: it does not say what a 'goal in effect' means (e.g. whether overlapping goals are returned, what happens when no goal exists, or how the range interacts with goal validity periods).

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 short sentence with no filler, and the resource is front-loaded. It is efficient, though the terseness borders on under-specification rather than crispness.

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?

An output schema exists and the input schema is fully documented, so the description need not explain return values or parameters. However, for a tool whose semantics hinge on 'goals in effect' over a range, the description leaves that concept undefined, which is a modest but real 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 100%, with both start_date and end_date fully documented including formats and defaults, so the schema carries the parameter burden. The description adds no extra meaning about how the date range filters goals, which is the baseline-3 outcome when the schema is complete.

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 a specific resource (weight goals) and a scope (in effect during a date range), which distinguishes it from the sibling get_weight that presumably returns measurements rather than goals. The verb is only implied by the tool name, but the resource and temporal scope are unambiguous.

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 explicit when-to-use guidance, no mention of when not to use it, and no reference to alternatives such as get_weight or get_profile_settings. The phrase 'in effect during a date range' hints at the use case but leaves the agent to infer it.

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