Gymdesk by Cotlet

Unfreeze a member in Gymdesk

gymdesk_unfreeze_a_member

Read-onlyIdempotent

Unfreeze a member 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_unfreeze_a_member"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 12, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Beyond the annotations (readOnlyHint, idempotentHint, destructiveHint=false), the description confirms the tool 'opens nothing by itself' and discloses the return content: step-by-step screens, buttons and fields. That is meaningful behavioral context an agent needs before deciding how to chain the call with browser tools.

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 operational sentence is front-loaded and useful, but the closing note about 404 API documentation on specific dates is verbose research chatter that does not help an agent select or invoke the tool. The entry-point framing ('from ChatGPT, Claude or any AI agent') is also redundant padding.

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, read-only instruction tool with no output schema, the description covers what it returns, that it is non-executing, and which tools complete the workflow. The only gap is the missing explicit contrast with the sibling freeze/unfreeze pair, which would make routing airtight.

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 the baseline is 4. Nothing in the description introduces ambiguity about inputs, and the empty schema is consistent with the described behavior.

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 ('Unfreeze a member') and scopes it to the user's own Gymdesk account. It is distinguishable from the sibling gymdesk_freeze_a_member by plain semantics, though it never names that sibling explicitly.

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 clearly routes the agent: this tool returns instructions only, and the actual action must be performed with cotlet_browser_* tools in the Gymdesk Cloud Browser. It does not spell out when to prefer this over alternatives such as the freeze tool, but the division of labor between planning and execution is explicit.

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?