Skip to main content
Glama

metri: Calorie & Macro Tracker

Set daily nutrition goal

metri_set_daily_goal
Idempotent

Use this when the user wants to set or change their daily calorie target and optional protein, fat, or carbohydrate targets. Returns the previous goal and today's progress against the new goal, shown as a card. The new goal applies from now on, including the rest of today; days that have already ended keep the goal they were lived against. Nothing is deleted: earlier goals are kept, and the goal can be changed back at any time.

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": {
      "kcal": "<kcal>"
    },
    "name": "metri_set_daily_goal"
  }
}

Input Schema

NameRequiredDescriptionDefault
fatNoDaily fat target in grams. Omit to keep the current fat target; null clears it.
kcalYesDaily calorie target in kcal.
carbsNoDaily carbohydrate target in grams. Omit to keep the current carbohydrate target; null clears it.
proteinNoDaily protein target in grams. Omit to keep the current protein target; null clears it.

Output Schema

NameRequiredDescriptionDefault
renderYesOrders the attached card among other metri cards.
dashboardYesToday's totals and the complete goal now in force (goal), including macro targets kept from the previous goal, as shown on the attached card.
previousGoalYesThe goal this call replaced, or null when the user had none. Set it again to undo the change.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Goes well beyond annotations by explaining that the previous goal is returned, today's progress is shown as a card, the new goal applies from now including the rest of today, ended days retain their old goal, nothing is deleted, and the change is reversible. These details clarify mutation scope and historical behavior despite annotations only saying the tool is idempotent and non-destructive.

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?

Three sentences with the action and trigger front-loaded, followed by useful return and persistence behavior. It is slightly verbose but every sentence carries relevant meaning.

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?

Complete for a goal-mutation tool: the trigger, optional parameters, return behavior, scope of change, and reversibility are all covered. An output schema exists, so the description does not need to detail response structure.

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?

With 100% schema description coverage, the schema already documents that omitted macro targets are kept and null clears them. The description mentions optional protein, fat, and carbohydrate targets but adds no syntax or semantics beyond the schema, so baseline 3 is appropriate.

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?

States a specific verb and resource: setting or changing daily calorie and optional macronutrient targets. It is clearly distinct from the sibling tools, which focus on food logging, editing consumption, and diary retrieval.

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?

Opens with explicit when-to-use guidance: 'Use this when the user wants to set or change their daily calorie target...' It covers the primary trigger and optional macros but does not name alternatives or exclusions.

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