Skip to main content
Glama

mywhoosh_get_profile

Retrieves MyWhoosh profile metrics including FTP, weight, height, and best power so you can check FTP before planning workout watt targets.

Instructions

FTP, weight, height and best power values stored in the MyWhoosh profile.

Workout targets in MyWhoosh are % of this FTP, so check it before planning watt targets.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations, the description carries the full burden; it makes clear this is a read of stored profile data and explains the meaning of the FTP value relative to workout targets. It says nothing about authentication requirements, whether the profile is user-scoped, or error behavior when no profile exists.

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, front-loaded with the returned fields and followed by the practical implication. The first sentence is a fragment rather than a complete statement of the action, and the trailing whitespace is noise, but nothing is padded.

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 zero-parameter read with no output schema, enumerating the returned fields and explaining the FTP semantics covers what an agent needs to call and interpret it. Minor gaps around scope (whose profile) and missing-profile handling keep it from full marks.

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, so there is nothing for the description to disambiguate and the baseline applies. The description instead spends its words on what the argument-free call returns, which is the more useful information here.

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?

The description enumerates the specific resource contents (FTP, weight, height, best power) from the MyWhoosh profile, which lets an agent tell it apart from the workout-oriented siblings and from mywhoosh_set_ftp. It lacks an explicit retrieval verb, so the read action is inferred from the field list rather than stated.

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?

It gives a concrete when-to-use rule: check this before planning watt targets, because MyWhoosh targets are percentages of this FTP. That is real actionable guidance with a stated rationale, though it does not explicitly name exclusions or the alternative for changing FTP (mywhoosh_set_ftp).

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