Skip to main content
Glama

metri: Calorie & Macro Tracker

Delete food consumption

metri_delete_consumption
DestructiveIdempotent

Delete an entire eating event and return the refreshed current-day dashboard. The operation is idempotent; use metri_edit_consumption to remove only one item.

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": {
      "consumptionId": "<consumptionId>"
    },
    "name": "metri_delete_consumption"
  }
}

Input Schema

NameRequiredDescriptionDefault
consumptionIdYesThe eating event to delete, from metri_get_diary or an earlier metri result.

Output Schema

NameRequiredDescriptionDefault
renderYes
dashboardYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is covered; the description adds genuine value by scoping the deletion to a whole eating event and disclosing the returned refreshed dashboard. The idempotency sentence largely restates the annotation, and reversibility/confirmation expectations are not addressed.

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: the action and its return are front-loaded, then the alternative-route hint. No filler and nothing repeated needlessly.

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?

For a single-parameter destructive tool with an output schema and full annotation coverage, the description supplies the essential scope, safety-adjacent idempotency note, and return context. Only minor gaps remain, such as whether deletion is recoverable and the delete_consumption vs delete_food boundary.

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 single consumptionId property already documents its source (metri_get_diary or an earlier metri result), so the schema does the heavy lifting. The description adds no further meaning about the identifier beyond what the schema states.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource plus scope ('an entire eating event') and mentions the refreshed dashboard return, which lets an agent distinguish it from a partial-removal tool. It stops short of clarifying how it differs from the sibling metri_delete_food, leaving one ambiguity among closely named tools.

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?

Explicitly names metri_edit_consumption as the alternative when only one item should be removed, giving a clear routing rule for the most likely confusion. It does not spell out when to prefer metri_delete_food or what preconditions (e.g. confirming the event id) are expected.

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