Skip to main content
Glama
Sign In
Wellness Nourish

Wellness Nourish

by davidmosiah
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Undo last entry

nourish_undo_last
Destructive

Undo the most recently logged meal or hydration entry to fix a mistaken nutrition log. Returns the removed entry for confirmation before you continue.

Instructions

Undo the most recently logged intake or hydration entry. The most common Telegram/agent recovery move ('I logged the wrong thing'). Returns what was undone so the agent can confirm. Requires explicit_user_intent. Pass kind: 'intake' | 'hydration' | 'any' (default 'any') to scope the undo.

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

Input Schema

NameRequiredDescriptionDefault
kindNoWhich most-recent entry to undo: 'intake' = last logged meal, 'hydration' = last logged water, 'any' = whichever was most recent across both stores. Defaults to 'any'.any
response_formatNojson
explicit_user_intentNoPass true only after the user explicitly asked to save, log, set, or delete this personal nutrition data.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.6

TDQS

A4.3/5.0
Behavior4/5

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

Beyond the annotations (destructiveHint=true), the description adds that the tool returns what was undone for confirmation and requires explicit_user_intent. This provides useful behavioral context beyond the schema and annotations.

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?

The description is three sentences long, front-loads the purpose, and contains no unnecessary words. Every sentence adds value.

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?

Given the tool's simplicity (undo last entry, kind scope, confirm return), the description covers purpose, parameters, behavioral requirements, and return value. No gaps for an agent to misunderstand.

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?

The description repeats the kind parameter values and emphasizes the explicit_user_intent requirement, but the schema already documents these parameters well (67% coverage). The description adds minimal new semantic insight.

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?

The description clearly states the tool undoes the most recent intake or hydration entry, using the verb 'undo' and specifying the resource. It distinguishes from siblings like nourish_delete_intake by focusing on the last entry and recovery context.

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?

The description provides context for use ('the most common Telegram/agent recovery move') and explains the kind parameter to scope the undo. It also notes the requirement for explicit_user_intent. However, it does not explicitly contrast with other delete/clear tools.

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

Deploy Server

Other Tools