Skip to main content
Glama

Nutrition

get_nutrition
Read-only

The user's nutrition goal (lose fat / maintain / build muscle), their daily calorie and macro targets and how they were worked out, and what they've logged in Splyt's food log day by day — each entry as they typed it, with calories, protein, carbs and fat (AI estimates). Use it to answer what and how much they should eat for their goal.

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

Input Schema

NameRequiredDescriptionDefault
daysNoDefault 7.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already establish this as a safe, local read, and the description adds genuinely new behavioral context: log entries are returned 'as they typed it' and macro values are flagged as AI estimates, which signals data-provenance reliability an agent should hedge on. It also discloses day-by-day granularity, though it does not mention pagination or what happens when no goal is set.

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?

Two sentences, no filler, and the second sentence is a clean, actionable usage statement. The first sentence is dense and em-dash-heavy, front-loading the goal and targets before the log entries, which is reasonable ordering but slightly harder to scan than a short lead clause would be.

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 must describe return contents, and it does so thoroughly — goal, targets, derivation, and per-entry macros — plus the AI-estimate caveat. Minor gaps remain (micronutrients, behavior when no target exists), but nothing essential for correct invocation is missing.

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% and the single 'days' parameter already documents its 1–30 range and default of 7, so the schema carries the parameter burden. The description's 'day by day' phrasing loosely implies a windowed query but adds no syntax or default detail beyond the schema; 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 enumerates exactly what the tool returns: the nutrition goal (with the three named goal values), daily calorie and macro targets with their derivation, and food-log entries with calories/protein/carbs/fat. The verb is implicit (a 'get' style read), but the resource and scope are specific enough to separate it from workout- and habit-oriented siblings.

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?

It gives a clear use context — 'Use it to answer what and how much they should eat for their goal' — which tells an agent the question shape this tool serves. It stops short of naming exclusions or alternatives (e.g., that it is not for exercise burn or body-weight trends), so it is clear context without routing.

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