Skip to main content
Glama

Nutrition log

get_nutrition_log
Read-onlyIdempotent

Get an athlete's logged nutrition (Food Journey) over the last days: daily calorie and macro totals against targets, a day-by-day join of fueling with training and its rule-based flags (for example an under-fueled long-run day), and recent logged foods. Status no_data means nothing was logged in the window. A coach sees it only when the athlete shares training data.

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": {
      "athlete_id": "<athlete_id>"
    },
    "name": "get_nutrition_log"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNoTrailing days to read, 1-30.
athlete_idYesThe athlete's user id: get_current_user's athlete_id for the connected account, or an id from get_coach_athletes or find_athlete.

Output Schema

NameRequiredDescriptionDefault
errorNo
statusNo
messageNo
privacyNoPresent when the athlete's settings withhold data.
targetsNo
timezoneNo
warningsNo
next_stepNoWhat can be done next, for example after a failure.
athlete_idNo
days_loggedNo
next_cursorNoReads the next page; null on the last page.
reason_codeNo
total_weeksNo
window_daysNo
daily_totalsNo
user_contentNoFields in this result that people wrote.
fueling_flagsNo
total_recordsNo
training_joinNo
recent_recordsNo
weeks_returnedNo
truncated_fieldsNoLists cut to fit one response: rows returned and total.
generated_contentNoFields in this result that NexRex's AI wrote.
session_definitionsNoSessions that several rows of this result share by session_ref.
content_block_fieldsNoColumn names of every content_blocks row, nested blocks rows included.
adherence_pct_of_targetNo
avg_calories_logged_daysNo
avg_protein_grams_logged_daysNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / properties / content_block_fields / description
      Previous value: -"Column names of every content_blocks row."New value: +"Column names of every content_blocks row, nested blocks rows included."
  2. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, non-destructive, closed-world), so the description is free to add the less obvious behavior — the no_data status sentinel and the authorization nuance that a coach only sees this when the athlete shares training data. That permission detail is exactly the kind of non-schema behavior an agent needs and would otherwise discover by failing.

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?

Three sentences, front-loaded with the purpose and contents before the two edge-case clauses. The parenthetical examples ('Food Journey', 'an under-fueled long-run day') earn their place by disambiguating domain jargon, though the first sentence is dense enough to be slightly heavy.

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 an output schema present, return-value detail is not owed, and the description still covers scope, the empty-result sentinel, and the share-permission gate. For a two-parameter read tool that is essentially complete; only the absence of any pointer to a related tool for deeper inspection keeps it from a 5.

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?

Schema description coverage is 100%: `days` is documented as 'Trailing days to read, 1-30' with a default of 7, and `athlete_id` already explains sourcing from get_current_user, get_coach_athletes, or find_athlete. The description only restates the trailing-window idea ('over the last `days`'), adding no syntax or edge-case meaning beyond the schema, so the baseline 3 applies.

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?

The description names a specific verb and resource ('Get an athlete's logged nutrition (Food Journey)') and then enumerates the actual payload: daily calorie and macro totals against targets, a day-by-day join of fueling with training plus rule-based flags, and recent logged foods. That level of concreteness lets an agent separate it from get_activities, get_training_status, or get_athlete_profile without opening the schema.

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?

Usage context is clear: read a trailing window of nutrition data, with the window bounded by the `days` parameter, and 'Status no_data means nothing was logged in the window' tells the agent how to interpret an empty result rather than retrying. It stops short of explicitly naming an alternative tool or stating when not to call it, so it is clear context without exclusions.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources