Skip to main content
Glama

Club OS by Cotlet

Freeze a member account in Club OS

club_os_freeze_a_member_account
Read-onlyIdempotent

Freeze 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_freeze_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?

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, and the description is consistent with them, reinforcing that the tool 'opens nothing by itself'. It adds genuinely useful behavior beyond the annotations: the return value is procedural steps (screens, buttons, fields) and the actual mutation must be done by separate 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose and the no-side-effect caveat are front-loaded in the first sentence, and the browser-handoff sentence earns its place. The closing note on Club OS's official API is relevant context but is slightly tangential and verbose for a tool that is purely instructional.

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 parameters, no output schema and permissive read-only annotations, the definition covers what an agent needs: what it returns, that it has no side effects, and where to go next. Minor gaps remain around prerequisites (authenticated Cloud Browser session) and error cases such as a member not being found.

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 parameter semantics to explain and the baseline of 4 applies. The description also correctly frames that the target account is not passed as an argument but resolved later in the browser workflow.

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 names a specific verb and resource (freeze a member account) and immediately clarifies the surprising part: it returns step-by-step instructions rather than performing the freeze. It does not explicitly distinguish itself from adjacent siblings such as club_os_cancel_a_member_account or club_os_manage_pt_agreement_freeze, which an agent could plausibly confuse with this operation.

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 states the intended follow-up path clearly ('then do it with the cotlet_browser_* tools in the user's Club OS Cloud Browser'), which gives an implied workflow. However it offers no explicit when-not-to-use guidance, no prerequisites (e.g. an active browser session), and no routing rule versus the official API beyond noting that API credentials require emailing support.

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