Skip to main content
Glama
Nutrition MCP
by ronkommoji

get_weekly_summary

Retrieve weekly calorie and protein averages, the best day, and tracked-day count for any ISO week to review nutrition progress.

Instructions

Return weekly calorie and protein averages, best day, and tracked-day count.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_weekly_summary"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNoAny YYYY-MM-DD date in the desired ISO week. Defaults to today.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It usefully discloses the shape of the result (averages, best day, tracked-day count), which signals a read-only aggregation, but it says nothing about permission requirements, behavior when the week has no logged days, or timezone/week-boundary handling.

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?

A single front-loaded sentence with zero filler; the enumerated return values are the most decision-relevant information and appear immediately.

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 simple, single-optional-parameter read tool with no output schema, the description covers what the agent gets back and the schema covers the input, so little is missing. Edge cases such as empty weeks or partial tracking are the only real gap.

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

Parameters3/5

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

There is one optional parameter and schema coverage is 100%; the schema already explains that any date in the target ISO week works and defaults to today. The description adds no further meaning about the date parameter or week resolution, so the baseline 3 applies.

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 uses a specific verb ('Return') and enumerates exactly what is returned: weekly calorie and protein averages, best day, and tracked-day count. The 'weekly' scope implicitly contrasts with get_daily_status, but no sibling is named explicitly, which keeps it just short of 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 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 tool for week-level trend questions rather than single-day status or food logging. There is no explicit when-to-use statement, no exclusions, and no mention of alternatives such as get_daily_status for per-day detail.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.