Gymdesk by Cotlet

Cancel future recurring membership payments in Gymdesk

gymdesk_cancel_future_recurring_membership_payments

Read-onlyIdempotent

Cancel future recurring membership payments in the user's own Gymdesk account from ChatGPT, Claude or any AI agent. Returns how to do it in Gymdesk step by step (screens, buttons, fields) and opens nothing by itself; then do it with the cotlet_browser_* tools in the user's Gymdesk Cloud Browser. Gymdesk's official API: No publicly documented Gymdesk API was found on 11 Nov 2026: gymdesk.com/api, gymdesk.com/developers and docs.gymdesk.com/api returned 404 and the help center has no Gymdesk API article.

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

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 12, 2026

TDQS

A4.2/5.0

Behavior5/5

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

The description resolves the tension between a destructive-sounding name and the readOnlyHint=true annotation by explicitly saying it 'opens nothing by itself' and only returns instructions. It also explains why the browser tools are required: no public Gymdesk API was documented, with the specific checks performed. This is context beyond what the annotations provide.

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?

It is dense but front-loaded, leading with the action and the actual return content before the API caveat. The final sentence about 404s on specific URLs and a date is unusual detail, though it does justify the browser-based workflow rather than being pure filler.

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?

With no output schema, the description tells the agent what comes back (screens, buttons, fields) and what the follow-up step is. It stops short of describing edge cases, such as what happens if there are no future recurring payments or if the user lacks permission, but it is adequate for a zero-parameter guidance tool.

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 the schema carries no semantics to explain and the baseline is 4. The description correctly implies no inputs are needed and does not fabricate any.

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 (cancel future recurring membership payments) and immediately clarifies the actual deliverable: step-by-step Gymdesk instructions rather than the cancellation itself. It does not explicitly distinguish this from closely related siblings such as gymdesk_modify_a_scheduled_membership_payment or the recurring-payment viewing tool, leaving a small ambiguity for an agent choosing between them.

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 gives a clear usage path: this tool returns the how-to, then the agent should perform the action with cotlet_browser_* tools in the user's Gymdesk Cloud Browser. It does not state when NOT to use it or name the sibling alternatives for modifying versus canceling a single scheduled payment.

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

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