Exercise.com by Cotlet

Backdate a client's subscription in Exercise.com

exercise_com_backdate_a_client_s_subscription

Read-onlyIdempotent

Backdate a client's subscription in the user's own Exercise.com account from ChatGPT, Claude or any AI agent. Returns how to do it in Exercise.com step by step (screens, buttons, fields) and opens nothing by itself; then do it with the cotlet_browser_* tools in the user's Exercise.com Cloud Browser. Exercise.com's official API: Exercise.com has an official API as a paid add-on: "API access is an additional feature with variable pricing", quoted by your Account Representative for your intended usage (checked 11 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": "exercise_com_backdate_a_client_s_subscription"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 12, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false. The description adds meaningful context beyond those annotations by stating that the tool opens nothing by itself and returns screen/button/field instructions, which is crucial for a tool whose name could imply direct mutation.

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?

The description is front-loaded with purpose and behavior, and the key operational detail about using cotlet_browser_* follows immediately. The final sentence about Exercise.com's official API pricing is tangential to invoking this specific tool, adding some noise without breaking overall clarity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-parameter, read-only instruction tool with no output schema, the description is complete: it says what the tool returns (step-by-step screens, buttons, fields), that it does not execute the action, and what to use afterward. An agent has enough information to call it correctly.

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 has zero parameters and 100% schema description coverage, so the baseline is 4. The description does not need to explain parameter syntax because no input parameters exist.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/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 (backdate a client's subscription) and explicitly clarifies that the tool returns step-by-step instructions rather than performing the action. It distinguishes itself from the execution tools by naming cotlet_browser_* as the next step, so an agent can identify its role without opening the schema.

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?

The description gives clear context: use this to get the Exercise.com steps, then perform the action with cotlet_browser_* tools in the Cloud Browser. It does not explicitly compare against other exercise_com_* siblings or state when not to use it, but the intended sequence is clear.

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

All Exercise.com 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?