Skip to main content
Glama

get_nutrition_daily_meals

Read-only

Retrieve daily meal summaries for a specific date, including nutritional totals per meal and meal IDs needed to log food items to breakfast, lunch, dinner, or snacks.

Instructions

Get daily meal summaries for a date

    Returns meal-level summaries (breakfast, lunch, dinner, snacks)
    with nutritional totals for each meal. Each meal includes a mealId
    needed for logging food items to that meal.

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

Input Schema

NameRequiredDescriptionDefault
dateYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, non-destructive, open-world behavior, so the description's added value is in disclosing the return payload: per-meal nutritional totals plus a mealId that enables subsequent logging. That is genuine behavioral context beyond the annotations, though it omits whether empty meals are returned or how the totals are keyed.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short paragraphs: the action first, then the return shape and the mealId affordance, with a compact args note. Every sentence carries information and nothing is padded.

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?

With no output schema, the description correctly spends its space describing the returned meal summaries and the mealId. For a single-optional-complexity read tool this is nearly sufficient; timezone handling and behavior on days with no logged meals are the only meaningful omissions.

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% — the schema only supplies a bare "Date" string title — so the description must carry the burden, and it does by specifying the YYYY-MM-DD format. It adds nothing about timezone or range semantics, which is the remaining gap.

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?

"Get daily meal summaries for a date" gives a specific verb and resource, and clarifies the granularity (meal-level: breakfast, lunch, dinner, snacks), which separates it in spirit from get_nutrition_daily_food_log. It never names the sibling or explicitly contrast with it, so an agent must infer the boundary.

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?

There is no explicit when-to-use or when-not-to-use statement and no named alternative. The line about mealId being "needed for logging food items to that meal" implies the natural follow-up workflow (fetch meals, then log food), but the routing guidance is left implicit.

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