Skip to main content
Glama
Sign In
garmin-mcp

garmin-mcp

by marcelfortmann
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

get_weight

Retrieve body weight, BMI, and body-fat percentage for a date range, with optional individual weigh-in entries. Defaults to the last four weeks.

Instructions

Body weight & body composition (weight, BMI, body-fat %) over a date range. Set include_raw for the individual weigh-in entries too. Default range: the last ~4 weeks.

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
endDateNoEnd date (YYYY-MM-DD). Default: today.
startDateNoStart date (YYYY-MM-DD). Default: ~4 weeks ago.
include_rawNoAlso include individual weigh-in entries. Default: false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.0.0
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. Changed1 schema field changedv1.1.1
    • removedInput schema / additionalProperties
      Removed value: -false
  3. First observedv1.0.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. It does disclose important behavior: the default window is ~4 weeks and the default response is aggregated rather than raw entries (implied by include_raw). It omits whether this is read-only, what the aggregation granularity is, and the response shape.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two tight sentences with zero filler, front-loaded with what is returned and followed by the key option and default. Nothing is wasted.

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?

All three parameters are optional and fully documented in the schema, and the description supplies the defaults and the aggregation-vs-raw distinction. Without an output schema, a bit more on the return shape would help, but the essentials for correct invocation are present.

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%, so the baseline is 3. The description reinforces include_raw's purpose and the default date window, but adds no format details or edge-case handling (e.g., empty ranges) 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?

States a specific verb implied (retrieve) and a concrete resource: body weight and body composition metrics (weight, BMI, body-fat %) over a date range. The metrics listed distinguish it from generic siblings like get_daily_health or get_fitness, though it never explicitly contrasts with them.

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?

Provides useful context — default range is the last ~4 weeks, and include_raw is the flag for per-weigh-in detail — which implies usage. However, it gives no explicit guidance on when to prefer this over siblings such as get_daily_health, get_fitness, or get_user_profile, leaving the agent to infer.

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