Skip to main content
Glama

metri: Calorie & Macro Tracker

Delete saved food

metri_delete_food
DestructiveIdempotent

Delete a saved food or batch: it disappears from metri_search_foods and can no longer be logged. Diary entries and batches that already contain it keep its name and nutrition.

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": {
      "foodId": "<foodId>"
    },
    "name": "metri_delete_food"
  }
}

Input Schema

NameRequiredDescriptionDefault
foodIdYesThe saved food or batch to delete, from metri_search_foods.

Output Schema

NameRequiredDescriptionDefault
nameYesName of the deleted food or batch.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=true, and openWorldHint=false, so the safety profile is largely pre-supplied. The description still earns credit by disclosing concrete post-conditions the annotations cannot convey: the item disappears from search results, can no longer be logged, and pre-existing diary entries retain its name and nutrition. It does not mention permissions or any recovery/undo path, which keeps it below a 5.

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 tight sentences with zero filler; the core action is front-loaded and the consequence clauses follow in order of importance. Every clause contributes distinct information.

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?

A single-parameter destructive delete with an output schema present, so return values need no explanation. The one thing an agent genuinely needs to know about a cascading delete — what survives and what does not — is explicitly covered.

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 100%, and the schema already explains that foodId is 'The saved food or batch to delete, from metri_search_foods.' The description merely restates that the target may be a food or a batch, adding no syntax, format, or edge-case guidance beyond the structured field. Baseline 3 applies when the schema carries the parameter semantics.

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 ('Delete') and precise resource ('a saved food or batch'), and immediately scopes the blast radius by noting diary entries that already contain it are unaffected. This implicitly distinguishes it from deleting consumption entries, so an agent can tell it apart from metri_delete_consumption without opening either schema.

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?

The description implies when to call it (to remove a saved food from the catalog) and points to metri_search_foods as the source of the id, but never states explicit when-to-use/when-not conditions or names metri_delete_consumption as the alternative for diary rows. Usage is inferable rather than spelled out.

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