FitSW MCP Server and API by Cotlet

Create workout in FitSW

fitsw_create_workout

Read-onlyIdempotent

Create workout in the user's own FitSW account from ChatGPT, Claude or any AI agent. Returns how to do it in FitSW step by step (screens, buttons, fields) and opens nothing by itself; then do it with the cotlet_browser_* tools in the user's FitSW Cloud Browser. FitSW's official API: FitSW publishes no public API, webhooks or Zapier app (checked 9 Nov 2026).

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

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 9, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Beyond the annotations, the description discloses the key behavioral fact that 'opens nothing by itself' and only returns screens/buttons/fields guidance, which explains and reinforces readOnlyHint=true rather than contradicting it. It also notes the absence of any official FitSW API, webhooks or Zapier app, saving an agent from looking for one. It does not cover prerequisites such as an already-open Cloud Browser session or failure behavior if the browser is unavailable.

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?

Three compact sentences, each carrying distinct information: what it returns, who performs the actual action afterward, and why no API route exists. The clarifying 'opens nothing by itself' is front-loaded where it matters most.

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 guidance tool embedded in a browser-automation workflow, the description covers mechanism, handoff and rationale well. What is missing is the prerequisite state (Cloud Browser open/signed in) and confirmation of what the returned step-by-step payload looks like in practice.

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; baseline 4 applies. The description's mention of the user's own account implicitly scopes the operation without needing an argument.

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 gives a specific verb and resource (create a workout in the user's FitSW account) and then immediately clarifies the real behavior: it returns step-by-step instructions rather than performing the creation. That nuance distinguishes it from the cotlet_browser_* siblings that do the actual work, though the name/title ('Create workout') remains slightly at odds with the read-only guide behavior and must be resolved by reading the body.

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 states the context of use (from ChatGPT, Claude or any AI agent) and names the counterpart tools explicitly: follow up with cotlet_browser_* in the user's FitSW Cloud Browser. It does not spell out exclusions (e.g., when not to use it, or what to do if no Cloud Browser session exists), so there is a small remaining gap.

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

All FitSW MCP Server and API by Cotlet tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?