Skip to main content
Glama

delete_activity

Destructive

Permanently delete a Garmin Connect activity: first call with confirm=false to preview, then call with confirm=true to confirm deletion.

Instructions

Permanently delete an activity from Garmin Connect.

    This cannot be undone. Call once with confirm=false (the default) to
    preview the activity, then call again with confirm=true to delete it.
    confirm=true is the scripting equivalent of a force flag.

    Args:
        activity_id: ID of the activity to delete
        confirm: Must be true to actually delete. Default false returns a 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": {
      "activity_id": "<activity_id>"
    },
    "name": "delete_activity"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmNo
activity_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/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 safety profile is largely covered. The description still adds genuine non-redundant behavior: the two-call preview-then-confirm protocol, the default value of confirm, and the explicit warning that the effect is irreversible. It omits return/response shape and permission requirements, which keeps it below a 5.

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 destructive verb and the irreversibility warning in the first two lines, which is the right ordering. The trailing 'Args:' block restates confirm/preview semantics already given in the prose, making it mildly redundant, but nothing is padded or off-topic.

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 two-parameter destructive tool with no output schema, the description supplies the essential safety behavior (irreversible, requires confirm=true, preview first). Given openWorldHint=true it could say more about account/scope prerequisites, but an agent has enough to call it correctly and safely.

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 must carry the parameters, and it does: activity_id is 'ID of the activity to delete' and confirm 'must be true to actually delete', with default false returning a preview. The one gap is that the schema accepts integer or string for activity_id, and the description never says string IDs are valid — a caller reading only the prose would assume an integer.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Opens with a precise verb+resource+scope: 'Permanently delete an activity from Garmin Connect.' That unambiguously separates it from the get_activity/set_activity_* siblings on the same resource. It does not explicitly name an alternative delete path, but none of the listed siblings deletes an activity, so the resource noun alone carries the differentiation.

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 a concrete usage protocol: call once with confirm=false to preview, then call again with confirm=true to actually delete, and frames confirm=true as the scripting equivalent of a force flag. Missing is any guidance on when not to use it (e.g. whether a different tool exists for bulk deletion) or any prerequisite/auth condition, but the when-and-how is clear.

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