Skip to main content
Glama

garmin_add_weigh_in

Record a body weight entry in Garmin Connect with optional kg/lbs unit and timestamp. Add measurements for now or a specified date and time.

Instructions

Record a weigh-in in Garmin Connect.

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": {
      "weight": "<weight>"
    },
    "name": "garmin_add_weigh_in"
  }
}

Input Schema

NameRequiredDescriptionDefault
unitNokg
whenNo'YYYY-MM-DD HH:MM', 'HH:MM' for today, or omit for now
weightYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.8/5.0
Behavior2/5

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

The annotations already establish a non-read-only, non-destructive operation, while the description adds only that the entry is recorded in Garmin Connect. It provides no further context about authentication, duplicate handling, timestamp timezone, or submission confirmation, and it does not contradict the annotations.

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?

The single sentence is front-loaded, direct, and free of filler. Its brevity is efficient but also omits useful differentiating and operational details, preventing it from being an ideally sized definition.

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?

A basic invocation is inferable because weight is required, unit is constrained to kg or lbs with a default, and when documents its accepted forms and current-time default. With no output schema and no explanation of the response, timezone behavior, or sibling boundaries, the definition is minimally adequate but has clear gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Only when has a schema description; weight and unit otherwise rely on their titles, types, enum, and default. The description adds no parameter meaning, such as explicitly connecting unit to weight or clarifying timestamp interpretation, so it does not compensate for the 33% schema description coverage.

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 gives a specific verb and resource—"Record a weigh-in"—and identifies Garmin Connect as the destination. It does not explain how this weight-only operation differs from the sibling garmin_add_body_composition tool.

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?

Recording a weigh-in provides only an implicit usage cue, with no explicit when-to-use or when-not-to-use guidance. In particular, it does not direct agents needing body fat or other composition metrics to garmin_add_body_composition.

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