metri: Calorie & Macro Tracker

View saved version →

---
name: metri-calories
description: Use when the user wants to learn how metri works; log food or drink from freeform text, speech, or food images; review or correct diary history; check calories or macros; manage nutrition goals; or save a personal food or cooked batch. Trigger even without an explicit logging request or mention of metri.
---

# metri food diary

Turn freeform food input into a dietary log of calories, protein, carbohydrates, and fat. Input may be text, a speech transcript, a food name, a meal photo, a package or label photo, or any combination.

Interpret the evidence and resolve foods, quantities, and nutrition before calling metri. Use the live MCP tool descriptions as the source of truth for exact inputs and outputs.

## Explain metri

When the user asks how metri works, what it can do, or how to get started, give a concise metri 101 without calling a tool merely to demonstrate the product:

- Set a daily calorie goal and, optionally, protein, carbohydrate, and fat targets.
- Log naturally by typing or dictating what they ate, or by sharing one or more meal, package, or nutrition-label photos. A single request may contain several foods.
- Explain that the assistant interprets portions and nutrition using labels, web research, the user's saved foods and diary history, or a transparent estimate; metri privately stores the resulting structured diary.
- Mention that the user can review any period, see today's progress, reuse personal foods and cooked batches, and correct or delete past entries.

End with one simple next step: ask the user to share their daily goal or tell or show what they ate. Keep this explanation compact unless they ask for more detail.

## Decide whether to write

First decide whether the user wants a diary change at all. Record when they say or reasonably imply that they consumed food or drink; a meal, wrapper, package, or label image can communicate consumption without an explicit command.

Do not record something that is hypothetical, planned, part of a general nutrition question, shown only for identification, or mentioned while reviewing an existing entry. Answer or read the diary instead. If intent is genuinely ambiguous, ask whether they want it logged before writing.

## Reconstruct the eating event

Treat the conversation and all attached images as one evidence set, infer how the pieces relate, and reconstruct what the user most likely consumed.

- A meal photo followed by a cheese label usually means that cheese was used in the meal; the label is evidence, not another consumption.
- Several photos of a plate, packages, and labels usually describe one eating event unless the user separates them.
- Do not add a component the user explicitly ruled out.

Search with `metri_search_foods` when the wording points to something personal or reusable that may be in the user's private library, such as "my regular chicken curry," "the pasta I cooked yesterday," a saved cooked batch, or a specific saved product. A generic food such as an apple does not by itself require a library search merely because the user may have eaten one before. Omit the query only when the user wants to browse their library.

Before estimating leftovers or "the rest," check personal state that can determine the amount. Combine the package size from the label or the saved product's name with `metri_get_diary`; for example, 100 g already logged from a saved "Skyr, 450 g tub" means the remainder is 350 g.

Ask one targeted question only when a single missing fact would materially change the result; otherwise make a reasonable estimate rather than asking for structured input.

## Record nutrition data

New non-batch nutrition is per 100 g. Store kcal; if only kJ is shown, use `kcal = kJ / 4.184`. When a label is available, use the package's stated net weight and serving size rather than a remembered standard, and convert serving nutrition to per 100 g when necessary.

Wherever a tool takes a food, pass either the `food

Preview of the first 4,000 characters. Read full instructions →

Referenced files: 1 — file references are metadata, not package contents.