Skip to main content
Glama

set_nutrition_daily_settings

Destructive

Update daily calorie and macronutrient goals for a specific date; only supplied fields change, so existing nutrition settings stay intact.

Instructions

Update daily nutrition goals (calorie target and macronutrient targets).

    Reads the current settings for the date, applies the supplied overrides,
    and writes the merged result back.  Only the fields you provide are
    changed; omitted fields keep their existing values.

    Macro arguments retain their existing names and are passed through to
    Garmin's macroGoals without unit conversion. The endpoint's macro units
    have not been independently verified. Returned goals come from Garmin's
    response, or a settings read-back when the update has no response body.

    Args:
        date: Date in YYYY-MM-DD format (settings are typically set once and
              inherited across days, but Garmin accepts per-day overrides)
        calorie_goal: Daily calorie target in kcal
        carbs_grams: Daily carbohydrate target in grams
        fat_grams: Daily fat target in grams
        protein_grams: Daily protein target in grams
        target_date: Optional new target date (YYYY-MM-DD) for the weight
              goal that this endpoint carries. Only needed when the stored
              target date has already passed, which otherwise makes Garmin
              reject the update; must be after `date`.
    

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": {
      "date": "<date>"
    },
    "name": "set_nutrition_daily_settings"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateYes
fat_gramsNo
carbs_gramsNo
target_dateNo
calorie_goalNo
protein_gramsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=false and openWorldHint=true, so the safety profile is covered. The description then adds genuinely new behavior: the read-modify-write merge model (omitted fields are preserved), that macro units passed to Garmin are unverified, and that returned goals may come from a read-back when the update has no body. That is substantive context beyond structured fields.

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 purpose is front-loaded, then behavioral rules, then per-parameter notes, which is the right ordering. The sentence about macro arguments retaining existing names and passing through to Garmin's macroGoals is somewhat implementation-detail heavy, but it earns its place by flagging the unit uncertainty.

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 destructive, non-idempotent write tool with no output schema and no schema descriptions, the definition covers input format, partial-update semantics, the rejection edge case, and where the returned values come from. Only auth/permission requirements and failure modes are absent.

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

Parameters4/5

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

With 0% schema description coverage, the description carries the full burden, and it does document all six parameters: date format YYYY-MM-DD, calorie_goal in kcal, the three macro targets in grams, and target_date with its ordering constraint relative to `date`. The individual macro definitions are thin (units inherited from names) and the unverified-unit caveat slightly reduces confidence, so it falls short of a 5.

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?

"Update daily nutrition goals (calorie target and macronutrient targets)" is a specific verb plus resource, and the read-merge-write sentence makes clear this is a mutating counterpart to the get_nutrition_daily_settings sibling. It stops short of naming the read sibling explicitly, which is why it isn't a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives a clear conditional for the tricky optional parameter (target_date is only needed when the stored target date has already passed, and must be after `date`) plus context that settings are typically set once and inherited. What's missing is any explicit statement about when to prefer this tool over the sibling getters or about prerequisites such as authentication.

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