Skip to main content
Glama

mywhoosh_set_ftp

Set your MyWhoosh cycling FTP in watts (50–600) by updating only the FTP field and verifying the rest of your profile stays unchanged.

Instructions

Set the cycling FTP in the MyWhoosh profile (watts, 50-600).

Rewrites the profile with only FtpPlayer changed and verifies that nothing else changed.

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": {
      "ftp_watts": "<ftp_watts>"
    },
    "name": "mywhoosh_set_ftp"
  }
}

Input Schema

NameRequiredDescriptionDefault
ftp_wattsYes

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?

With no annotations present, the description carries the full burden and does disclose non-obvious behavior: the profile is rewritten with only FtpPlayer changed and the tool verifies nothing else changed — a read-modify-write with an integrity check. It omits error behavior for out-of-range values and any return/response shape, which keeps it from a 5.

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?

Two short sentences, zero filler, with the core action and constraint front-loaded. Every clause carries information an agent could act on.

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 single-parameter setter with no output schema and no annotations, the definition covers the essential facts: what is changed, the valid range, and the safety behavior of the rewrite. A note on prerequisites or failure modes would make it 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?

Schema coverage is 0% and the schema only declares an integer named 'ftp_watts', so the description adds real meaning: the unit (watts) and the accepted range (50-600). It does not say what unit the value is interpreted in beyond watts or how out-of-range input is handled, but the range is the critical missing piece and it is supplied.

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 states a specific verb and resource: "Set the cycling FTP in the MyWhoosh profile." It is unmistakably distinct from the workout CRUD/list siblings and the profile reader. It falls short of a 5 only because it doesn't explicitly name the counterpart operation (e.g., mywhoosh_get_profile) it complements.

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?

Usage is implied by the verb: use it to change FTP. There is no explicit when-to-use vs. when-not guidance, no prerequisites (e.g., profile must already exist, authentication), and no statement about what to do when the desired value falls outside 50-600 watts.

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