Gymdesk by Cotlet

Create and manage discount codes in Gymdesk

gymdesk_create_and_manage_discount_codes

Read-onlyIdempotent

Create and manage discount codes 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_create_and_manage_discount_codes"
  }
}

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?

Beyond the readOnlyHint/idempotentHint annotations, the description discloses what the tool actually returns (screens, buttons, fields, step by step) and explicitly states it "opens nothing by itself" and requires separate browser tools to execute — exactly the kind of non-obvious behavior an agent needs. This is consistent with, and additive to, the supplied annotations.

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 front-loaded: purpose first, then what it returns, then the execution path via browser tools. The closing paragraph citing 404s for gymdesk.com/api and docs.gymdesk.com is somewhat verbose, but it does earn its place by explaining why browser automation is required instead of an API call.

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 input schema and no output schema, the description carries the burden of explaining what comes back, which it does (step-by-step UI instructions). It does not say what discount-code attributes the steps cover (amount vs. percentage, expiry, limits), a minor gap for a guidance-only 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 baseline is 4 and there is nothing for the description to disambiguate. The absence of parameters is also implicitly consistent with the described behavior of returning guidance only.

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 ("Create and manage discount codes in the user's own Gymdesk account") and clarifies that it returns step-by-step instructions rather than performing the action. It is clearly distinguishable from siblings like gymdesk_manage_referral_rewards or gymdesk_create_digital_gift_cards by resource, though it never explicitly contrasts itself with 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 execution context: get the steps here, then "do it with the cotlet_browser_* tools in the user's Gymdesk Cloud Browser." That is explicit next-step routing, but there is no when-not-to-use guidance or comparison against adjacent tools such as gift cards or referral rewards.

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?