Skip to main content
Glama

get_cycling_ftp

Read-only

Retrieve the current cycling Functional Threshold Power (FTP) estimate from Garmin to track training thresholds and set power zones.

Instructions

Get the latest cycling Functional Threshold Power (FTP) data.

Returns the most recent cycling FTP estimate available from Garmin.

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_cycling_ftp"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds one genuinely useful behavioral detail beyond them — that it returns only the most recent estimate available from Garmin rather than a time series — but says nothing about what happens when no FTP estimate exists (error vs. empty result).

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?

Two short sentences with the purpose front-loaded and no filler. Minor redundancy between "latest" in the first sentence and "most recent ... estimate available" in the second, which restates the same temporal constraint.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a trivial no-parameter read tool with full annotation coverage, the definition covers what it fetches but not what it returns — no mention of the value's unit (watts), whether a measurement date or source device accompanies it, or the empty-result behavior. With no output schema, the description is the only place that could carry this, so a moderate gap remains.

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?

The tool takes zero parameters and the schema is an empty object, so there is nothing for the description to disambiguate. Baseline 4 applies for a no-parameter tool.

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 and resource: "Get the latest cycling Functional Threshold Power (FTP) data," which is concrete and distinguishable from the sibling data getters (activities, body battery, blood pressure). It stops short of naming any sibling or explicitly scoping itself against a non-cycling FTP counterpart, so it is clear but not maximally differentiated.

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

Usage Guidelines2/5

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

The description offers no when-to-use guidance, no prerequisites (e.g., that the account needs a recorded cycling FTP or a compatible device), and no alternatives. The only usage signal is implicit: the word "latest" suggests a single current value rather than a history lookup.

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