Skip to main content
Glama

log_food

Quick-add a food entry to Garmin Connect's nutrition log by name and macros, with meal assigned automatically from the entry time or defaulting to snacks.

Instructions

Quick-add a food entry with macro values to the nutrition log

    Logs food directly by name and macros without requiring a food ID.
    Uses Garmin's Quick Add feature. The meal is determined automatically
    by matching meal_time against each meal's startTime/endTime window;
    falls back to SNACKS if no window matches.

    Args:
        meal_date: Date in YYYY-MM-DD format
        name: Display name for the food entry
        calories: Calories (kcal)
        carbs: Carbohydrates in grams
        protein: Protein in grams
        fat: Fat in grams
        meal_time: Time in HH:MM:SS format (account timezone)
    

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": {
      "meal_date": "<meal_date>",
      "meal_time": "<meal_time>",
      "name": "<name>",
      "calories": "<calories>",
      "carbs": "<carbs>",
      "protein": "<protein>",
      "fat": "<fat>"
    },
    "name": "log_food"
  }
}

Input Schema

NameRequiredDescriptionDefault
fatYes
nameYes
carbsYes
proteinYes
caloriesYes
meal_dateYes
meal_timeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

Beyond the annotations (readOnlyHint=false, openWorldHint=true, idempotentHint=false), the description discloses a non-obvious behavior: the meal is auto-derived by matching meal_time against each meal's startTime/endTime window, falling back to SNACKS when nothing matches. That is real behavioral context that the schema and annotations cannot convey. It does not say that repeated calls create duplicate entries, which matters given idempotentHint=false.

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 opening sentence is front-loaded and the Args block is scannable, but the second sentence partially restates the first ("logs food directly by name"), and the docstring section repeats parameter names already visible in the schema. Minor redundancy rather than bloat.

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 seven-required-parameter mutation with no output schema, the description covers the essential mechanics: units, formats, and how the meal is resolved. Gaps are the lack of any note on duplicate entries or what the call returns, but with all parameters required and the meal logic explained, an agent can call it correctly.

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

Parameters5/5

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

Schema description coverage is 0%, so the description carries the full burden, and it delivers: every one of the seven parameters is documented with units (kcal, grams) or format (YYYY-MM-DD, HH:MM:SS in account timezone). The account-timezone note is a substantive clarification the schema does not provide.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Quick-add a food entry with macro values to the nutrition log" gives a specific verb, resource and mechanism, and the follow-up line "Logs food directly by name and macros without requiring a food ID" cleanly separates it from sibling tools that operate on custom foods/serving IDs.

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?

The description establishes clear context for when this tool applies (free-form quick entry with its own macros, no food ID needed), which implicitly routes the agent away from food-ID-based logging siblings. It stops short of explicitly naming an alternative such as log_custom_food or upsert_and_log, so the choice is left partly to inference.

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