Skip to main content
Glama

metri: Calorie & Macro Tracker

Save food

metri_save_food
Destructive

Create a reusable non-batch food, or update one by foodId: only the fields passed change. Does not log consumption.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "metri_save_food"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoFood name. Required when creating.
foodIdNoThe saved food to update. Omit to create a new food.
nutritionPer100gNoNutrition per 100 g. Required when creating.

Output Schema

NameRequiredDescriptionDefault
nameYes
foodIdYes
warningsNo
nutritionPer100gYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare mutation, non-idempotency, and destructiveHint=true, so the safety profile is supplied. The description adds one genuinely useful behavioral fact — 'only the fields passed change' (partial update semantics) — but says nothing about why a save is marked destructive, whether omitting the nested nutritionPer100g object replaces or preserves it, or what overwriting an existing food does.

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?

Two short sentences, front-loaded with the create/update dual behavior, with the exclusion clause placed last. No filler or restated title.

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?

With a full-coverage schema, an output schema, and annotations covering safety, the description is nearly sufficient for calling the tool. The residual gap is update semantics for the nested nutritionPer100g object on an existing food.

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 coverage is 100% and the schema already states 'Omit to create a new food' and 'Required when creating', so the description's foodId framing largely restates structured data. The one addition is the partial-update rule for omitted fields; nested object replace-vs-merge semantics remain unexplained in both places.

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 ('Create a reusable non-batch food, or update one by foodId') and marks the scope boundaries against siblings in the same sentence: 'non-batch' excludes metri_save_batch and 'Does not log consumption' excludes metri_log_consumption. An agent can classify the tool without opening the schema.

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?

It gives the create-vs-update switch (pass foodId to update, omit to create) and an explicit exclusion ('Does not log consumption'), which routes consumption logging elsewhere. It does not name the sibling tool to use instead for logging, so it falls short of a full when/when-not/alternative triad.

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