Skip to main content
Glama

get_nutrition_summary_between_dates

Read-only

Retrieve per-day nutrition totals (calories, carbs, protein, fat, item_count) across a date range to analyze multi-day intake and estimate TDEE without fetching full daily food logs.

Instructions

Get per-day nutrition totals for every day in a date range.

    Returns one lightweight entry per day (date, calories, carbs, protein,
    fat, item_count) instead of the full per-item food log that
    get_nutrition_daily_food_log returns for a single date. Use this for
    multi-day intake analysis (e.g. mean intake for a TDEE estimate)
    instead of calling get_nutrition_daily_food_log once per day.

    item_count is the number of logged food items that day. A day with
    item_count == 0 has no logged food at all, and a low but nonzero
    item_count may mean only part of the day was logged (e.g. breakfast
    only). Both cases read as low intake in the totals alone -- exclude
    low-item_count days explicitly before averaging intake or deriving
    TDEE; don't infer "unlogged" from a low calorie total.

    Maximum range: 61 days per call (Garmin's own limit for this endpoint).

    Args:
        start_date: Start date in YYYY-MM-DD format
        end_date: End date in YYYY-MM-DD format
    

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": {
      "start_date": "<start_date>",
      "end_date": "<end_date>"
    },
    "name": "get_nutrition_summary_between_dates"
  }
}

Input Schema

NameRequiredDescriptionDefault
end_dateYes
start_dateYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered; the description adds real context beyond them, namely the 61-day per-call endpoint limit and the interpretability caveat around item_count and partial logging. It does not state pagination or empty-range behavior, which is the main remaining gap.

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?

Front-loads the core purpose and the sibling comparison before detailing return fields and data-quality caveats; each section earns its place. The item_count paragraph is the longest block but justifies itself by preventing a concrete analysis error, though it could be tightened slightly.

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

Completeness5/5

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

No output schema exists, so the description compensates by enumerating the returned fields (date, calories, carbs, protein, fat, item_count), and it covers the range limit and data-quality pitfalls. For a two-parameter read tool this is complete enough to call correctly.

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?

Schema coverage is 0%, so the description must carry the burden, and it does: it specifies the YYYY-MM-DD format for both dates and constrains the end_date relative to start_date via the 61-day maximum range. It does not say whether the range is inclusive or how invalid or reversed ranges are handled.

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?

States a specific verb and resource ('Get per-day nutrition totals for every day in a date range') and explicitly contrasts the output shape with the sibling get_nutrition_daily_food_log. An agent can distinguish this from the single-date tool without opening either schema.

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

Usage Guidelines5/5

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

Gives explicit when-to-use guidance: multi-day intake analysis such as mean intake for a TDEE estimate, and tells the agent not to loop the single-date sibling. It also adds when-not-to-trust guidance, warning that low-item_count days should be excluded before averaging rather than inferred as unlogged from low calorie totals.

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