Skip to main content
Glama
sedoglia

Garmin Connect MCP Server

by sedoglia
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Delete Weigh-In

delete_weigh_in
Destructive

Remove a single Garmin weigh-in permanently using its unique ID. Specify the original date only if the entry was backdated; deletion cannot be undone.

Instructions

Permanently delete a single weigh-in record, identified by its weigh-in ID (the samplePk from get_weigh_ins or get_body_composition). The measurement cannot be recovered afterwards. Pass date when the weigh-in was back-dated to a day other than the one it was entered on.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dateNoDate of the weigh-in in YYYY-MM-DD format. Defaults to the day the weigh-in id encodes, which is the day it was recorded.
weighInIdYesThe unique weigh-in identifier (required)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv4.5.7
    • addedInput schema / properties / date
      Added value: +{
+  "description": "Date of the weigh-in in YYYY-MM-DD format. Defaults to the day the weigh-in id encodes, which is the day it was recorded.",
+  "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
+  "type": "string"
+}
  2. First observedv4.3.0

TDQS

A5/5.0
Behavior5/5

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

Annotations already indicate destructiveHint, and the description reinforces it by stating 'permanently delete' and 'cannot be recovered afterwards'. Also clarifies that it deletes a single record and explains the date parameter behavior.

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 concise, uses two sentences, front-loads the core action, and includes all essential details without redundancy. Well-structured.

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 simplicity of the operation (delete by ID), the description covers the action, identification, irreversibility, and the optional parameter usage. No output schema is needed, so it is complete for an agent.

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?

The schema only gives types and patterns, but the description adds meaning: weighInId is the samplePk from get_weigh_ins or get_body_composition, and date is used when the weigh-in was back-dated. This goes beyond the schema.

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 (delete) and resource (weigh-in record), specifies it is permanent and single, and identifies the ID source. Clearly distinguishes from sibling tools like delete_blood_pressure or delete_workout.

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?

Provides clear guidance on when to use this tool: for deleting a single weigh-in record. Explains when to pass the optional date parameter (when the weigh-in was back-dated). Does not explicitly contrast with alternatives like add_weigh_in, but the scope is unambiguous.

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