Skip to main content
Glama

delete_food_log

Destructive

Permanently removes a logged food item from the Garmin nutrition log after previewing the matching entry; confirm to complete deletion.

Instructions

Delete a food log entry

    Permanently removes a logged food item from the nutrition log.
    Works for both QUICK_ADD and REGULAR_LOG entry types.
    Use get_nutrition_daily_food_log to find the logId and date. The default
    call previews the matching entry; call again with confirm=true to delete.

    Args:
        log_id: Log entry ID to delete — a 32-char hex UUID
            (from get_nutrition_daily_food_log)
        meal_date: Date of the log entry in YYYY-MM-DD format
        confirm: Set true to delete after reviewing the default preview
    

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": {
      "log_id": "<log_id>",
      "meal_date": "<meal_date>"
    },
    "name": "delete_food_log"
  }
}

Input Schema

NameRequiredDescriptionDefault
log_idYes
confirmNo
meal_dateYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare destructive=true and non-idempotent, but the description adds genuinely new behavior: that the default call is a non-destructive preview and a second call with confirm=true performs the permanent removal. It does not cover what happens if the log_id is not found or already deleted, which is a smaller gap given the annotation coverage.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the verb and permanence, then workflow, then parameters. The 'Args:' block with trailing blank lines is slightly verbose formatting but every sentence carries actionable information.

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 3-parameter destructive tool with no output schema, the definition covers identification, format, the preview-confirm safety mechanism, and which entry types apply. Only error/not-found behavior is unaddressed.

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

Parameters5/5

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

Schema coverage is 0%, so the description carries the full burden and does so: log_id is a 32-char hex UUID sourced from get_nutrition_daily_food_log, meal_date is YYYY-MM-DD, and confirm is the true-flag that triggers actual deletion after preview.

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 ('Delete a food log entry', 'Permanently removes a logged food item from the nutrition log') and scopes it to QUICK_ADD and REGULAR_LOG entry types, which an agent can act on without opening 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?

Names the prerequisite tool ('Use get_nutrition_daily_food_log to find the logId and date') and spells out the two-step workflow: the default call previews, then confirm=true deletes. Both when-to-use and the exact invocation path are given.

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