Skip to main content
Glama

Club OS by Cotlet

Cancel a member account in Club OS

club_os_cancel_a_member_account
Read-onlyIdempotent

Cancel a member account in the user's own Club OS account from ChatGPT, Claude or any AI agent. Returns how to do it in Club OS step by step (screens, buttons, fields) and opens nothing by itself; then do it with the cotlet_browser_* tools in the user's Club OS Cloud Browser. Club OS's official API: Club OS has an official API for its calendar, agreements, leads, follow-ups and KPIs, but credentials come only by emailing Club OS support to set up an account (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": "club_os_cancel_a_member_account"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

The annotations declare readOnlyHint=true and destructiveHint=false, which superficially clashes with a tool named "cancel"; the description resolves that by stating it "opens nothing by itself" and only returns instructions, so the read-only profile is coherent. It also discloses the practical constraint around API credentials (email support, checked date). Return content is described at a high level (screens, buttons, fields).

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 operative content is front-loaded and clear, but the trailing paragraph about Club OS's official API and the support-email onboarding is tangential to invoking this specific tool and inflates the definition. The mention of third-party agent names adds little for an agent reader.

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

Completeness3/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 tool, the description covers what is returned and that nothing is executed, which is the essential part. However, it never explains how the target member is identified with no parameters at all — presumably from Cloud Browser state — which is a meaningful gap for correct invocation.

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 input schema takes zero parameters, so there is no per-parameter meaning for the description to add and the baseline of 4 applies. Nothing in the description contradicts or muddies the empty schema.

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 gives a specific verb and resource ("Cancel a member account in the user's own Club OS account") and, critically, clarifies that the tool only returns step-by-step instructions rather than performing the cancellation. It does not explicitly distinguish itself from close siblings such as club_os_freeze_a_member_account or club_os_delete_an_employee_account, so the sibling differentiation is only partly there.

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?

Usage is spelled out: this tool produces guidance, then the agent must act via the cotlet_browser_* tools in the user's Club OS Cloud Browser. It also notes the official API path requires emailing support, which is useful routing context. What is missing is when to choose cancel versus freeze or delete for a given member situation.

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