Skip to main content
Glama

Club OS by Cotlet

Add a new lead in Club OS

club_os_add_a_new_lead
Read-onlyIdempotent

Add a new lead 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_add_a_new_lead"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Beyond the annotations (readOnlyHint, idempotent, non-destructive, openWorld=false), the description adds substantive behavior: the tool opens nothing by itself, returns screens/buttons/fields guidance, and requires a follow-up step with browser tools. That is exactly the kind of context an agent needs to avoid assuming the lead is already created. The dated parenthetical ('checked 11 Nov 2026') is a stray detail rather than transparency.

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?

Three sentences, front-loaded with purpose and mechanism, with zero redundant restatement of the name. The official-API sentence is somewhat tangential to invoking this tool but earns its place by pre-empting an agent's attempt to use the API instead, though the future-dated check adds noise.

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 and no output schema, the description correctly carries the burden of explaining what comes back (step-by-step Club OS instructions) and what must happen next (browser tools). An agent has everything needed to call it and interpret the result; only a pointer to a preferred sibling for pure lead creation is missing.

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 for the description to add or omit; baseline 4 applies. The description does not misdescribe any input requirements.

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 and resource (add a new lead in the user's Club OS account) and immediately clarifies the actual mechanism: it returns step-by-step instructions rather than performing the write. That resolves the tension between the name 'add_a_new_lead' and the readOnly annotation. It does not distinguish itself from similar creation-path siblings such as club_os_use_the_digital_guest_waiver_to_create_a_prospect, so it falls short of a 5.

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 context for use: from an AI agent, followed by execution via the cotlet_browser_* tools in the user's Club OS Cloud Browser. It also explains why the official API is not a viable shortcut (credentials require emailing Club OS support), which is genuinely useful routing guidance. It stops short of explicit exclusions or named alternative club_os_* tools for lead creation.

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