Skip to main content
Glama

Bulk freeze, cancel or reactivate members in Gymdesk

gymdesk_bulk_freeze_cancel_or_reactivate_members
Read-onlyIdempotent

Bulk freeze, cancel or reactivate members 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_bulk_freeze_cancel_or_reactivate_members"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, but the description adds the crucial disclosure that this tool merely returns a recipe (screens, buttons, fields) and performs no action itself, which resolves the tension between its name and its annotations. It does not cover things like output size or whether the guide varies by action type, but the key behavioral surprise is disclosed.

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 core purpose and the browser hand-off are front-loaded and efficient, but the closing API paragraph (404 URLs, a specific date, 'no Gymdesk API article') is long, situational, and tangential to invoking the tool. The 'from ChatGPT, Claude or any AI agent' clause is also 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?

For a zero-parameter, no-output-schema guide tool, the description covers what it returns and what to do next, which is sufficient to call it. It stops short of explaining how the target members or the specific action (freeze vs cancel vs reactivate) are conveyed, given there are no inputs at all.

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 there is no schema semantics to supplement; baseline for a parameterless tool applies. The description adds that the response is an instruction sequence rather than data, which is the relevant 'parameter-free' context an agent needs.

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+resource (return step-by-step Gymdesk instructions for bulk freeze/cancel/reactivate of members) and explicitly reframes a name that sounds like a mutation. It distinguishes itself from executing siblings by saying it 'opens nothing by itself', though the single-vs-bulk discriminator against gymdesk_freeze_a_member comes from the word 'Bulk' rather than an explicit comparison.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives a clear follow-on workflow ('then do it with the cotlet_browser_* tools in the user's Gymdesk Cloud Browser'), which tells the agent this is step one of a two-step process. However, it never states when NOT to use it or names an alternative among the many gymdesk_* siblings, so the selection guidance is implied rather than explicit.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources