Skip to main content
Glama
Nutrition MCP
by ronkommoji

undo_last_log

Removes the most recent food log entry to correct accidental or incorrect calorie tracking, with an optional YYYY-MM-DD date to target a specific day.

Instructions

Remove the most recent food log entry, optionally constrained to a specific date.

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": "undo_last_log"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNoOptional YYYY-MM-DD date.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose the blast radius: exactly one entry, the most recent, optionally narrowed by date. It does not state whether the removal is reversible, what happens when no entry exists (error vs. no-op), or what the tool returns, which are notable gaps for a destructive operation.

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 sentence with the action and its scope front-loaded and no filler. Every clause carries information, including the optional narrowing behavior.

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 one-parameter, no-output-schema tool the description covers the core action adequately, but given that it is a destructive mutation with no annotations, the missing failure-mode and result information leaves an agent guessing about edge cases such as an empty log or a date with no entries.

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 parameter is already documented as an optional YYYY-MM-DD string. The description adds real meaning by explaining what the parameter does semantically: it constrains which "most recent" entry is targeted, rather than being a required identifier.

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?

"Remove the most recent food log entry" states a concrete mutation verb plus a precisely scoped resource, which clearly separates it from log_food, search_food_history, and the summary tools. It stops short of naming a sibling explicitly, but the scope (only the most recent entry) makes misselection unlikely.

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 optional date constraint implies the two usage modes (undo latest overall vs. undo latest within a day), but neither is spelled out as a when-to-use rule. There is no guidance on prerequisites, on when not to call it, or on what to do if the intended entry is not the most recent one.

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