Skip to main content
Glama

delete_weigh_ins

Destructive

Delete weight measurements for a specific date in Garmin Connect. Preview the selected day's weigh-ins first, then confirm to permanently remove them.

Instructions

Delete weight measurements for a specific date

    Permanently removes the selected day's weigh-ins. This cannot be undone.
    Call once with confirm=false (the default) to preview the measurements,
    then call again with confirm=true to delete them.

    Args:
        date: Date in YYYY-MM-DD format
        delete_all: Whether to delete all measurements for the day
        confirm: Set true after reviewing the preview to perform the deletion
    

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>"
    },
    "name": "delete_weigh_ins"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateYes
confirmNo
delete_allNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=false, and openWorldHint=true, so the base bar is lower; the description still adds real value by stating that deletion is permanent and irreversible and by prescribing a preview-then-confirm workflow. It does not say what the preview actually returns or what happens to measurements when delete_all is false, which are the remaining behavioral unknowns.

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?

The core warning and the confirm workflow are front-loaded in the first sentences, with the argument list at the end. The Args block partly restates parameter names, but each entry adds at least the date format or a usage note, so it mostly earns its space.

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 three-parameter destructive tool with no output schema and no annotation beyond the safety hints, the description covers irreversibility, the preview workflow, and the date format. The gaps are the unspecified return value of the preview call and the undefined semantics of delete_all=false, both of which matter for calling it correctly.

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 description coverage is 0%, so the description has to carry all three parameters, and it does: date is given an explicit YYYY-MM-DD format, confirm is tied to the preview workflow, and delete_all is identified as 'delete all measurements for the day'. The delete_all explanation is thin — it never says what is deleted when it is false, and with no measurement identifier parameter that branch is genuinely ambiguous.

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 opens with a specific verb and resource plus a scope qualifier ('Delete weight measurements for a specific date'), and the follow-up sentence clarifies that it is permanent removal of a day's weigh-ins. This is clearly distinguishable from siblings like get_weigh_ins, get_daily_weigh_ins, and add_weigh_in without needing to open any schema.

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?

It gives an explicit two-step invocation protocol: call with confirm=false (the stated default) to preview, then call with confirm=true to delete. It does not say when a caller should prefer a different deletion path or what to do if only some measurements should be removed, so it stops short of full when/when-not guidance.

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