cronometer-mcp

Overview Schema Source Related Servers Discussions Admin

add_food_entry

Add a food entry to your Cronometer diary by specifying food ID, source, weight in grams, and date for accurate nutrition tracking.

Instructions

Add a food entry to the Cronometer diary.

Use search_foods to find food_id and food_source_id, then get_food_details for measure_id and weight_grams.

For CRDB/custom foods, you can omit measure_id (defaults to a universal NCCDB measure that works for all food sources). When measure_id is omitted, quantity is set to weight_grams.

Args: food_id: Numeric food ID from search_foods results. food_source_id: Food source ID from search_foods results. weight_grams: Weight of the serving in grams. date: Date to log the entry as YYYY-MM-DD (e.g. "2026-03-04"). measure_id: Measure/unit ID. Pass 0 (default) to use the universal measure that works for all food sources. quantity: Number of servings. Defaults to weight_grams when measure_id is 0 (universal gram-based measure). diary_group: Diary group name (case-insensitive) or 0-based index. Names are user-configured and are not always Breakfast/Lunch/Dinner/Snacks — call list_diary_groups to see this account's groups. Defaults to a time-of-day choice among enabled groups if omitted.

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": {
      "food_id": "<food_id>",
      "food_source_id": "<food_source_id>",
      "weight_grams": "<weight_grams>",
      "date": "<date>"
    },
    "name": "add_food_entry"
  }
}

Input Schema

Name	Required	Description	Default
`date`	Yes
`food_id`	Yes
`quantity`	No
`measure_id`	No
`diary_group`	No
`weight_grams`	Yes
`food_source_id`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedv2.2.0Aug 24, 2026
- addedInput schema / properties / diary_group / anyOf
```
Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "integer"
+  },
+  {
+    "type": "null"
+  }
+]
```
- changedInput schema / properties / diary_group / default
```
Previous value: -"Breakfast"New value: +null
```
- removedInput schema / properties / diary_group / type
```
Removed value: -"string"
```
First observedv2.0.3Mar 21, 2026

TDQS

A4.8/5.0

Behavior4/5

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

With no annotations provided, the description carries the behavioral burden. It discloses default behavior for measure_id, quantity, and diary_group fallback, and warns that diary group names are user-configured and may differ from standard ones. It does not detail side effects or error handling, but it covers the most decision-relevant behavior.

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 organized as a compact workflow paragraph followed by an Args list. Every sentence adds value, and the structure front-loads the primary action before parameter detail.

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

Completeness5/5

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

Given the tool's 7 parameters, 0% schema coverage, and no annotations, the description is remarkably complete. It covers the calling sequence, parameter sources, defaults, edge cases for CRDB/custom foods, and how to discover diary groups, leaving no important gap for an agent to invoke it correctly.

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 description coverage is 0%, and the description compensates fully by explaining the origin and purpose of every parameter, including food_id, food_source_id, weight_grams, date, measure_id, quantity, and diary_group. It also clarifies relationships like quantity defaulting to weight_grams when measure_id is 0.

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 first sentence states the specific operation and resource: "Add a food entry to the Cronometer diary." It clearly distinguishes itself from sibling tools like remove_food_entry and get_food_log, and the workflow references tie it to search_foods and get_food_details.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

The description explicitly prescribes a workflow: use search_foods to find IDs, get_food_details for measure and weight, and list_diary_groups for valid group names. It also explains when measure_id and quantity can be omitted for CRDB/custom foods, giving precise selection guidance.

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