Skip to main content
Glama
Nutrition MCP
by ronkommoji

log_food

Store a confirmed food entry with calories and protein once the user approves the estimate.

Instructions

Store a confirmed food entry. The agent supplies calories and protein (estimated with its own knowledge or web search). Requires userConfirmed: true.

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": {
      "rawEntry": "<rawEntry>",
      "calories": "<calories>",
      "protein": "<protein>",
      "userConfirmed": "<userConfirmed>"
    },
    "name": "log_food"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNoYYYY-MM-DD date. Defaults to today in the profile timezone.
notesNoOptional assumptions or context, e.g. 'assumed 2 large eggs'.
sourceNoOptional source, e.g. a URL used to estimate.
proteinYesProtein grams to log.
caloriesYesCalories to log.
rawEntryYesFood description, e.g. '2 eggs and toast'.
timestampNoISO timestamp. Defaults to now.
userConfirmedYesMust be true; the user confirmed the estimate before logging.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations, the description carries the burden alone. It usefully discloses that this is a permanent stored record, that the confirmation gate is mandatory, and that the agent is responsible for estimating calories/protein itself, but it is silent on what a successful call returns, whether duplicate entries are possible, and what happens if userConfirmed is false.

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?

Three short sentences, front-loaded with the action, then the data-ownership expectation, then the hard gate. No filler and nothing buried.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For an 8-parameter mutation tool with no annotations and no output schema, the description covers the confirmation requirement and the estimation responsibility but omits the return shape and failure behavior. Adequate to invoke correctly, not complete.

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 100%, so a 3 is the baseline, but the description adds real meaning beyond the schema: it explains where the calories/protein numbers are supposed to come from (agent estimation or web search), which the schema fields do not say. That provenance guidance is a genuine supplement rather than a restatement.

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?

"Store a confirmed food entry" names a specific verb (store) and resource (food entry), and adds a distinguishing qualifier ("confirmed") that separates it from the read-only siblings like search_food_history and from the inverse action undo_last_log. It stops short of explicitly naming a sibling to defer to, which keeps it off 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 Guidelines4/5

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

It states a clear precondition for use: the entry must be user-confirmed and userConfirmed must be true. It does not spell out when to choose this over alternatives (e.g., search first vs. log directly), so it is clear context without explicit exclusions.

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