Skip to main content
Glama

Edit a food entry

trainrec_edit_food

Changes fields of one food entry, given its id and version. Fields left out stay as they are; perServing is replaced whole. planned: false marks a planned food eaten, with servings or perServing in the same call as what was actually had.

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": {
      "id": "<id>",
      "version": "<version>"
    },
    "name": "trainrec_edit_food"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
dayNo
mealNo
nameNo
plannedNofalse: eaten. true: planned, not eaten yet.
summaryNo
versionYes
servingsNo
perServingNoFor ONE serving, as the label or a reliable source states it.
servingLabelNo

Schema Changelog

Changes observed during successful MCP inspections.

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

TDQS

A3.7/5.0
Behavior4/5

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

The annotations already establish that this is a non-destructive mutation, and the description adds meaningful behavioral details: omitted fields remain unchanged, perServing is replaced whole, and planned:false can convert a planned food into an eaten one in the same call. It does not explain version-conflict behavior or error handling, but it provides solid context beyond the annotations.

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?

The description is three tight sentences with no wasted wording. The core edit behavior is front-loaded, and the important caveats about omitted fields, perServing replacement, and planned:false follow logically.

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?

The definition conveys enough to understand the core partial-update behavior, but for a 10-parameter mutation tool with nested perServing data and no output schema, it omits important context such as version-conflict handling and the meaning of several editable fields. It is adequate but not complete for the tool's complexity.

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 only 20%, so the description must carry more weight. It usefully clarifies perServing replacement, planned semantics, and the relationship between servings/perServing when marking a planned food as eaten, but it leaves day, meal, name, summary, servingLabel, and version semantics largely to the schema.

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 clearly states that this tool changes fields of one food entry identified by id and version, so the verb and resource are specific. It does not explicitly distinguish itself from sibling tools such as log_food, import_food, or delete_food, which keeps it from 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 implied by the requirement for id and version, indicating an existing entry rather than a new one. The description also gives one concrete usage rule for setting planned to false and eating a planned food, but it does not explicitly say when to use this tool instead of log_food, import_food, or delete_food.

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