Skip to main content
Glama

get_cycling_ftp

Retrieve your latest cycling Functional Threshold Power (FTP) from Garmin Connect to track performance and set training zones.

Instructions

Get latest Functional Threshold Power (FTP) for cycling

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Tool registration for 'get_cycling_ftp' via server.registerTool. No input schema needed (no parameters). Calls client.getCyclingFTP() and returns JSON-stringified result.
    server.registerTool(
      'get_cycling_ftp',
      {
        description: 'Get latest Functional Threshold Power (FTP) for cycling',
      },
      async () => {
        const data = await client.getCyclingFTP();
        return {
          content: [{ type: 'text' as const, text: JSON.stringify(data, null, 2) }],
        };
      },
    );
  • Handler method getCyclingFTP() on GarminClient. Makes a GET request to CYCLING_FTP_ENDPOINT.
    async getCyclingFTP(): Promise<unknown> {
      return this.request(CYCLING_FTP_ENDPOINT);
    }
  • Constant CYCLING_FTP_ENDPOINT defining the API endpoint path for latest cycling functional threshold power.
    export const CYCLING_FTP_ENDPOINT = '/biometric-service/biometric/latestFunctionalThresholdPower/CYCLING';
Behavior3/5

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

No annotations are provided, so the description must carry the burden of behavioral disclosure. It indicates a read operation ('Get'), which is non-destructive, but does not elaborate on any side effects or assumptions. For a simple getter without parameters, this is adequate but minimal.

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?

The description is a single sentence that conveys the essential information without any unnecessary words. It is front-loaded and efficient.

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?

Given the tool's simplicity (no parameters, no output schema), the description is sufficient to understand what the tool does. It could mention the return type or value, but for a getter of a single metric, the current description is nearly complete.

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 input schema has zero parameters, so schema coverage is 100% by default. The description does not need to add parameter semantics, and the baseline score of 4 applies for no parameters.

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?

The description explicitly states 'Get latest Functional Threshold Power (FTP) for cycling', using a specific verb and resource. It clearly distinguishes this tool from the many other 'get_' siblings by specifying the exact metric (FTP) and activity type (cycling).

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?

The description does not provide any guidance on when to use this tool versus alternatives or when not to use it. The usage is implied by the purpose, but there is no explicit mention of context or exclusion criteria.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Nicolasvegam/garmin-connect-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server