Skip to main content
Glama

get_activity_power_in_timezones

Read-only

Retrieves time spent in each power training zone for a Garmin activity, including watt thresholds and duration, using the athlete's FTP to show power distribution.

Instructions

Get power distribution across training zones for an activity.

    Returns time spent in each power zone with watt thresholds and duration.
    Requires a power meter. Zones are based on the athlete's FTP configured in Garmin Connect.

    Args:
        activity_id: ID of the activity to retrieve power zone data for
    

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": "get_activity_power_in_timezones"
  }
}

Input Schema

NameRequiredDescriptionDefault
activity_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false. The description adds meaningful behavior beyond them: the response reports time spent per zone with watt thresholds and duration, and zones depend on FTP configured in Garmin Connect. Error behavior when no power data exists is not covered, but that is a minor gap given the annotations.

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?

Front-loads purpose and return content, then prerequisites, then the single argument. The Args block is compact and earns its place given zero schema description coverage.

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?

For a simple one-parameter read-only tool with no output schema, the description covers purpose, return shape, prerequisite, zone basis, and the parameter. Nothing critical for correct invocation is missing.

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%, so the description must compensate; it names activity_id and explains it as the ID of the activity to retrieve power-zone data for. It does not clarify why the schema accepts either an integer or a string, but for a single required parameter this is minimally adequate.

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?

States a specific verb ('Get') and resource ('power distribution across training zones for an activity'), and describes the return content. It does not explicitly contrast with siblings such as get_activity_hr_in_timezones, so differentiation relies on the word 'power' rather than stated guidance.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Implies the tool is for power-zone analysis and gives the prerequisite 'Requires a power meter' plus the FTP basis for zones. It does not say when to prefer it over related tools like get_power_duration_curve or the HR-zone sibling, so usage guidance remains implied.

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