CoachingPortal by Cotlet

Manage personal workout in CoachingPortal

coachingportal_manage_personal_workout

Read-onlyIdempotent

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

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

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 11, 2026

TDQS

A3.8/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and idempotentHint=true, and the description is consistent with them ('opens nothing by itself'). It usefully adds that the response is a step-by-step procedure and that execution must happen via the Cloud Browser tools, but it does not say how granular or long that procedure is or how failures surface. Solid additive context, short of rich behavioral disclosure.

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?

Three sentences, front-loaded with the behavior and followed by the required next step. The 'from ChatGPT, Claude or any AI agent' clause is mild filler that could be trimmed, but everything else carries information.

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?

No output schema, but the description compensates by stating what is returned (step-by-step screens, buttons, fields) and how it is consumed. With zero parameters and a stated read-only profile, this is close to complete; only the range of workout operations covered under 'manage' is left open.

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?

Zero parameters, so there is no schema semantics to supplement; baseline 4 applies. The description correctly signals a parameterless tool by describing the call as a pure lookup of a procedure.

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 resource is specific ('personal workout in the user's own account') and the description correctly reframes the verb: the tool does not manage the workout itself, it returns a step-by-step how-to. However, 'manage' remains broad (create vs. edit vs. delete a workout) and nothing distinguishes it from coachingportal_manage_workout_block or coachingportal_log_pt_workout.

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?

Explicit sequencing guidance: call this first to get screens/buttons/fields, then perform the action with the cotlet_browser_* tools. It also rules out an API path ('CoachingPortal publishes no public API'). Missing is an explicit exclusion, e.g. when to prefer a sibling tool for coach-side or block-level workout work.

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

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