garminconnect-js

delete_heart_rate_zones

Destructive

Removes a sport's custom heart rate zone profile so it reverts to the DEFAULT zones. This action is irreversible and refuses to delete the DEFAULT profile.

Instructions

Removes a sport's own zone profile; it falls back to DEFAULT. PUTs the stored profile back with changeState: "DELETED", which removes it so the sport falls back to DEFAULT. Refuses DEFAULT; throws for a sport with no profile instead of doing nothing. IRREVERSIBLE: confirm with the user before calling.

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": {
      "sport": "<sport>"
    },
    "name": "delete_heart_rate_zones"
  }
}

Input Schema

Name	Required	Description	Default
`sport`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 15, 2026

TDQS

A4.2/5.0

Behavior5/5

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

Annotations only declare destructiveHint/readOnlyHint/openWorldHint; the description goes well beyond that by disclosing the fallback-to-DEFAULT semantics, the underlying PUT with changeState "DELETED", the two failure modes (refuses DEFAULT, throws on missing profile), and an explicit irreversibility warning with a confirmation requirement.

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

Conciseness3/5

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

Front-loads the core effect and ends with the most safety-critical sentence, which is good. However, the fallback-to-DEFAULT behavior is stated twice ('it falls back to DEFAULT' then 'which removes it so the sport falls back to DEFAULT'), wasting a clause.

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 single-parameter destructive tool with no output schema, the description covers effect, side effects, error behavior, and irreversibility. The remaining gap is the expected input format for 'sport' and whether a caller must first verify a profile exists.

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?

Schema description coverage is 0% for the single 'sport' parameter, so the description must compensate. It adds meaningful semantics — 'sport' selects a sport-specific profile and the reserved value DEFAULT is rejected — but does not clarify the accepted format (name vs. numeric sport ID), leaving an ambiguity for the caller.

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 (removes/deletes), a precise resource (a sport's own heart-rate zone profile), and the consequence (falls back to DEFAULT). This clearly distinguishes it from get_heart_rate_zones and set_heart_rate_zones among the numerous sibling tools.

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?

Gives explicit when-not conditions: it refuses the DEFAULT sport and throws when the sport has no profile rather than silently no-op'ing, plus a 'confirm with the user before calling' instruction. It does not name the sibling alternatives (get/set_heart_rate_zones) an agent might use instead, so it stops short of a 5.

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

Deploy Server