Skip to main content
Glama
health-os

health-os

delete_meal

DestructiveIdempotent

Remove a meal from the food diary and the nutrient totals — only when the user says it was logged by mistake or twice (food_log_id from query_food). To fix a time, portion or nutrients use update_meal instead.

Instructions

Remove a meal from the food diary and the nutrient totals — only when the user says it was logged by mistake or twice (food_log_id from query_food). To fix a time, portion or nutrients use update_meal instead.

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": {
      "food_log_id": "<food_log_id>"
    },
    "name": "delete_meal"
  }
}

Input Schema

NameRequiredDescriptionDefault
food_log_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.3.0

TDQS

A4.7/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 still adds real value by noting the deletion also alters nutrient totals, which is a side effect not visible in the annotations. It stops short of saying whether the user should be asked to confirm or whether deletion is recoverable, leaving one small behavioral gap.

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 sentences, no filler, with the destructive scope stated first and the routing caveat second. Every clause earns its place.

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?

With an output schema present, rich annotations, and a single required parameter, the description covers everything an agent needs: what is removed, what it affects, when to call it, and where the ID comes from.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so the description must carry the parameter, and it does by giving the value's provenance ("food_log_id from query_food"). It does not describe the expected format (e.g., UUID vs. integer string), which is the one remaining ambiguity for a single-param tool.

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 ("Remove a meal from the food diary and the nutrient totals") and immediately distinguishes itself from update_meal and, by implication, log_meal. An agent can tell exactly what this tool does without reading 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 Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit precondition ("only when the user says it was logged by mistake or twice") and names the correct alternative for the adjacent case ("To fix a time, portion or nutrients use update_meal instead"). It is a model of when-to-use / when-not-to-use guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.