Skip to main content
Glama

Log food

trainrec_log_food

Adds one or more food entries, each with its numbers PER SERVING and the number of servings. perServing takes the macros and any label nutrient (sodiumMg, potassiumMg and the rest); a nutrient left out counts as unknown, not zero. A glass of plain water is an entry named "Water" with kcal and macros 0 and waterMl. Each entry is its own change, with Undo. When the person asks to note a food without numbers ("just note it"), leave perServing out: it shows as numbers not added yet, until edit_food gives it perServing. planned: true puts a meal on a day ahead (or later today) without counting it in any total until it is eaten (edit_food planned: false).

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": {
      "entries": "<entries>"
    },
    "name": "trainrec_log_food"
  }
}

Input Schema

NameRequiredDescriptionDefault
entriesYes
summaryNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / entries / items / properties / planned
      Added value: +{
      +  "description": "Planned, not eaten yet.",
      +  "type": "boolean"
      +}
  2. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations only declare a non-destructive write; the description adds real behavior: each entry is an independent change that can be Undone, omitted nutrients are unknown rather than zero, and planned meals stay out of every total until eaten. It does not discuss authentication, rate limits, or what the response returns, but the core mutation semantics are disclosed.

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?

Front-loads the per-serving constraint, then layers water, undo, no-numbers, and planned cases in priority order with zero filler. It is a dense single paragraph and phrases like "and the rest" are slightly loose, but no sentence is wasted.

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?

Complete for a two-parameter write tool with no output schema: conventions, deferred counting, undo, and the edit_food follow-up are all covered. Minor gaps are the role of servingLabel and of the summary field, though the schema supplies descriptions for both.

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

Parameters5/5

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

Schema coverage is reported at 0%, so the description carries the burden and does it well: perServing is per-one-serving macros and label nutrients, servings is the multiplier, perServing may be omitted entirely, planned defers counting, and waterMl is the water convention. Only servingLabel, day, and summary are left to the schema, which documents day and servingLabel.

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?

Opens with a specific verb and resource ("Adds one or more food entries") and immediately pins the critical scope: numbers are PER SERVING plus a serving count. It also distinguishes the tool from edit_food by naming the handoff for planned meals and for entries saved without numbers.

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?

Gives concrete when-to-use cases: logging water as a "Water" entry with waterMl, entering a food with no numbers ("just note it"), and putting a meal on a future day via planned. The alternative, edit_food with planned: false, is named with the condition that selects it. No guidance on duplicates or when to prefer import_food over manual entry.

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