Skip to main content
Glama

Club OS by Cotlet

Merge duplicate accounts in Club OS

club_os_merge_duplicate_accounts
Read-onlyIdempotent

Merge duplicate accounts 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_merge_duplicate_accounts"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and idempotentHint=true, and the description reinforces this consistently with 'opens nothing by itself' — a meaningful disclosure that no state changes occur. It also tells the agent what the output looks like (step-by-step screens, buttons, fields) and notes the official-API credential constraint. It stops short of covering prerequisites such as admin permissions needed to actually merge in Club OS.

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 core purpose and the 'returns instructions, opens nothing' clarification are front-loaded, which is exactly the right ordering. The trailing sentence about Club OS's official API is longer than its relevance warrants, though it does justify why browser automation is the chosen path rather than a distraction with no purpose.

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 helper tool, the description covers what it returns, what it does not do, and which tool family completes the task. The only gap is the absence of any note on prerequisites (account permissions, what counts as a duplicate) that would affect a successful follow-through.

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 and the schema confirms an empty object, so there is nothing for the description to disambiguate. Baseline 4 applies; no parameter meaning is missing.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb and resource ('Merge duplicate accounts in the user's own Club OS account') and immediately clarifies the tool's actual nature: it returns step-by-step instructions rather than performing the merge. That distinction separates it cleanly from the operational siblings listed (e.g. club_os_add_a_new_lead, club_os_cancel_a_member_account), which act on data.

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 gives clear usage context: call this to get the screens/buttons/fields walkthrough, then perform the work with the cotlet_browser_* tools in the Cloud Browser. It also implicitly rules out the official API path by explaining credentials require emailing support. What's missing is an explicit 'when not to use this' for cases where the user already knows the steps or lacks browser-tool availability.

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