Skip to main content
Glama

get_nutrition_daily_food_log

Read-only

Retrieve daily food logs for a specific date, including calories, macronutrients, and meal associations.

Instructions

Get daily food consumption records for a date

    Returns food items logged throughout the day including calories,
    macronutrients, and meal associations.

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

Input Schema

NameRequiredDescriptionDefault
dateYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds useful behavioral detail about the returned payload (logged food items with calories, macros, and meal associations), but says nothing about timezone handling for "date", behavior on days with no logs, or result size.

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 sentence is front-loaded and the return summary follows immediately; nothing is padded. The Args block is slightly redundant with the schema but it is where the YYYY-MM-DD format is conveyed, so it earns its place.

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 one-parameter read tool with annotations covering safety and no output schema, the description supplies both the input format and a sketch of the return payload. The remaining gap, timezone/date-boundary semantics, is minor rather than blocking.

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 description coverage is 0%, so the description must carry the parameter, and it does: it specifies the date format as YYYY-MM-DD, which the bare schema does not. No further semantics (timezone, accepted ranges) are given, but for a single date param this is adequate.

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 ("Get daily food consumption records") scoped to a single date, and it names what is returned (calories, macronutrients, meal associations). It does not explicitly distinguish itself from the close sibling get_nutrition_daily_meals, so differentiation is left to the reader.

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

Usage Guidelines3/5

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

Usage is only implied: an agent can infer this is the per-day food log tool and that a date must be supplied, but there is no statement of when to prefer it over get_nutrition_daily_meals or get_nutrition_summary_between_dates, nor any exclusions or prerequisites.

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