Skip to main content
Glama

Club OS by Cotlet

Delete an employee account in Club OS

club_os_delete_an_employee_account
Read-onlyIdempotent

Delete an employee 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_delete_an_employee_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 and destructiveHint=false, and the description reconciles the alarming 'delete' name with them by explicitly saying it 'opens nothing by itself' and only returns instructions — that prevents a serious misread. It also discloses that the official API exists but that credentials require emailing Club OS support, saving the agent a dead-end attempt. It stops short of describing the shape or length of the returned steps.

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 operative behavior ('returns steps, opens nothing, then use browser tools') is front-loaded and the API note is a single purposeful sentence of context. Some filler remains, notably 'from ChatGPT, Claude or any AI agent' and the restatement of the account scope, which add length without decision value.

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 annotations covering the safety profile, the description carries what matters: what is returned, that nothing is executed, and which tool family completes the action. The main remaining gap is the absence of a sibling comparison for revoke-vs-delete, which matters for a destructive-sounding employee operation.

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, which is the baseline 4 case; there is nothing for the description to disambiguate. Implicitly the description explains why no parameters exist — the guide is generic and the targeting happens in the browser tools or conversation.

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?

Names a specific verb and resource (delete an employee account) and then corrects the natural reading by stating it 'Returns how to do it in Club OS step by step (screens, buttons, fields) and opens nothing by itself' — so the agent learns this is a guidance/instruction tool, not an executor. It does not differentiate against close siblings such as club_os_revoke_or_restore_an_employee_s_access, so the boundary between deleting an account and revoking access is left unstated.

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 next-step rule: use the cotlet_browser_* tools in the Club OS Cloud Browser to actually perform the deletion, which is real routing guidance. It does not say when to prefer this over the revoke/restore sibling, nor whether the official API is ever an alternative for this specific action, so the when-not side is only implied.

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