Skip to main content
Glama

get_power_duration_curve

Read-only

Computes season power-duration curve records from recent activities, returning mean maximal power at standard durations with source activity/date; use 20-minute power ×0.95 as an FTP estimate.

Instructions

Get season-best Power Duration Curve across recent activities.

    Downloads FIT files for recent activities of the requested type and computes best mean maximal
    power at each standard duration. Returns season bests with which activity and date
    each best came from.

    Durations: 5s (sprint), 30s, 1min, 5min (VO2 max proxy), 10min, 20min (FTP proxy), 60min

    Use the 20-minute best × 0.95 as a strong FTP estimate without a formal test.

    Warning: downloads multiple FIT files — may take 30-60 seconds for 20 activities.

    Args:
        num_activities: Number of recent activities matching activity_type to request
                        (default 20, max 50)
        activity_type: Activity type to filter (default "cycling")
    

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_power_duration_curve"
  }
}

Input Schema

NameRequiredDescriptionDefault
activity_typeNocycling
num_activitiesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

Beyond the readOnly/openWorld annotations, it discloses the costly behavior (downloads multiple FIT files, 30-60 seconds for 20 activities) and what the result contains (season bests plus source activity and date). The duration checkpoints and FTP-proxy interpretation add further practical context; only error/partial-failure behavior is unstated.

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 summary sentence, then mechanism, output shape, durations, guidance, and a warning, so the important cost signal is visible before the parameters. The Args block partly restates the schema fields, though it earns its place by adding the max-50 limit.

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?

With no output schema, the description still explains the return value (season bests with the originating activity and date). Combined with latency warning, duration list, and full parameter semantics, nothing material is missing for correct invocation.

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?

Schema description coverage is 0%, and the description fully compensates: it explains num_activities as the count of recent matching activities with default 20 and max 50, and activity_type as an activity-type filter defaulting to 'cycling'. Both parameters gain meaning not present in the bare 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 and resource ('season-best Power Duration Curve across recent activities') plus the mechanism (downloads FIT files, computes mean maximal power per duration). This distinguishes it from activity-listing siblings and from get_cycling_ftp, which it explicitly relates to as a test-free FTP estimate.

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 clear use case (FTP estimation without a formal test via 20-min best × 0.95) and bounds on scope (recent activities matching activity_type, 20 default / 50 max). It does not explicitly say when to prefer get_cycling_ftp or other siblings instead, so guidance is contextual rather than comprehensive.

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