Skip to main content
Glama
mijneetmeter-mcp

mijneetmeter-mcp

by jhofstede

delete_food

Destructive

Delete a diary entry by consumption_id from get_diary or get_diary_day, specifying the date and meal to remove the item.

Instructions

Delete a diary entry by its consumption_id (from get_diary or get_diary_day).

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": {
      "date": "<date>",
      "meal": "<meal>",
      "consumption_id": "<consumption_id>"
    },
    "name": "delete_food"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateYesDate in DD-MM-YYYY format
mealYesMeal moment: ontbijt/breakfast, lunch, avondeten/dinner, tussendoor/snack
consumption_idYesconsumption_id of the entry

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior2/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false, and openWorldHint=true, so the safety profile is covered by structured data. The description adds nothing beyond that — no statement on permanence, whether a confirmation step exists, or what happens when the ID does not match the date/meal. For a destructive operation, that is a real gap rather than a minor one.

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?

A single front-loaded sentence with zero filler: the action, the identifying input, and where to get it. Nothing is padded or restated from the schema.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a three-required-parameter destructive tool with no output schema, the description correctly identifies what gets deleted and where the ID comes from. It leaves open the behavior on mismatched date/meal, invalid IDs, and irreversibility, which an agent needs before invoking a delete.

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 100%, so the baseline is 3, and the description earns an extra point by documenting the provenance of consumption_id, which the schema only labels as "consumption_id of the entry." It still says nothing about whether the supplied date and meal must match the entry's own date and meal.

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?

The description gives a specific verb and resource ("Delete a diary entry") plus the key identifying parameter, so it is clearly distinguishable from add_food or the read-only diary tools. It stops short of explicitly naming the inverse sibling it complements, but the action itself is unambiguous.

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?

It supplies a genuine prerequisite: the consumption_id must come from get_diary or get_diary_day, which routes the agent through a read step first. It offers no when-not guidance (e.g., what to do if the entry is already gone) and no comparison against any alternative deletion path.

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