Skip to main content
Glama

garmin_set_nutrition_goals

Set daily calorie and macro goals in Garmin Connect for a specific date to track nutrition precisely.

Instructions

Set Garmin Connect's daily calorie and macro goals from a date.

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_set_nutrition_goals"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNoYYYY-MM-DD, 'today' or 'yesterday'today
fat_gNo
carbs_gNo
protein_gNo
target_dateNoWeight-goal date; needed when Garmin's stored one has passed
calorie_goalNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=false, so the write-but-not-destructive profile is covered. The description adds nothing about what happens to goals not supplied (preserved vs. cleared), whether a call with all-null parameters is a no-op, or whether the change is per-day or persistent. With annotations carrying the safety profile, this is a modest but real gap rather than a critical one.

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 front-loaded sentence with no filler. It is efficient, though its brevity is part of why the behavioral and parameter detail is missing.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This is a six-parameter, all-optional mutation tool with no output schema and no stated return behavior. An agent cannot tell from the definition what a partial update does or what success looks like, which is exactly the information this description should supply.

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?

Schema description coverage is only 33%, with fat_g, carbs_g, protein_g, and calorie_goal undocumented, and the description does not compensate: it never explains units, valid ranges, or the crucial question of whether omitted macros leave existing goals untouched. It only restates the field groups already implied by the parameter names.

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 uses a specific verb ('Set') plus resource ('Garmin Connect's daily calorie and macro goals') and a date scope, which is enough to distinguish it from read-oriented siblings like garmin_nutrition. The phrase 'from a date' is slightly ambiguous (presumably 'for a date'), but the intent remains legible.

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 guidance on when to use this versus garmin_nutrition (viewing goals) or garmin_log_food (logging intake), and no mention of prerequisites such as an existing Garmin nutrition profile. The agent must infer the routing from the tool name alone.

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