FitBudd MCP Server and API by Cotlet

Schedule workout in FitBudd

fitbudd_schedule_workout

Read-onlyIdempotent

Schedule workout in the user's own FitBudd account from ChatGPT, Claude or any AI agent. Returns how to do it in FitBudd step by step (screens, buttons, fields) and opens nothing by itself; then do it with the cotlet_browser_* tools in the user's FitBudd Cloud Browser. FitBudd's official API: FitBudd publishes no public API; its developer docs return "gone".

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

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 9, 2026

TDQS

A3.9/5.0

Behavior4/5

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

The annotations already state read-only, non-destructive, idempotent, and closed-world behavior. The description adds useful context beyond those annotations: it returns step-by-step UI instructions with screens, buttons, and fields; it performs no action itself; and FitBudd has no public API. It could say more about the exact return format, but the key behavioral traits are disclosed.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core message is front-loaded, but 'from ChatGPT, Claude or any AI agent' is filler and the final sentence about developer docs returning 'gone' is awkward and only marginally useful. The description could be significantly tighter without losing meaning.

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 guide tool with annotations and no output schema, the description explains what is returned (step-by-step instructions) and what to do next (use the browser tools). The exact output shape is not specified, but that is a minor gap given the tool's simplicity.

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?

There are zero parameters, so there are no parameter semantics to document. The baseline score of 4 applies because the description does not need to compensate for missing schema details.

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 specifies that this tool returns a step-by-step guide for scheduling a workout in FitBudd, not that it performs the scheduling itself ('returns how to do it ... opens nothing by itself'). That resolves the potentially misleading tool name and distinguishes it from the cotlet_browser_* execution tools. It is clear, though the name still implies an action rather than guidance.

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 explains the intended flow: call this to get instructions, then use cotlet_browser_* tools in the user's FitBudd Cloud Browser to carry them out. The boundary 'opens nothing by itself' is explicit. It does not directly compare against fitbudd_* sibling tools, but the guidance is sufficient for this narrow guide-style tool.

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

All FitBudd 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?