Skip to main content
Glama

Club OS by Cotlet

Turn on automatic follow-ups in Club OS

club_os_turn_on_automatic_follow_ups
Read-onlyIdempotent

Turn on automatic follow-ups 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_turn_on_automatic_follow_ups"
  }
}

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, idempotentHint=true and destructiveHint=false; the description is consistent with them and adds the crucial fact that nothing is opened or changed by the call itself. It also discloses the content of the response (screens, buttons, fields) and the API availability caveat, adding real context beyond annotations.

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 key point (returns steps, opens nothing) is front-loaded, and the browser-tool follow-up is stated immediately after. The trailing official-API sentence is slightly tangential and the opening phrase partly restates the title, but neither is wasted text.

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 a read-only annotation set, the description covers what an agent needs: what it returns, that it is inert, and how to act on the result. Only the precise shape of the returned steps is left unspecified, which is a minor gap for a zero-parameter tool.

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 schema takes zero parameters at 100% description coverage, so there is nothing for the description to disambiguate. Baseline 4 applies; the description correctly signals that no input is required.

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?

States a specific verb and resource (turn on automatic follow-ups in the user's Club OS account) and immediately clarifies the actual behavior: it returns step-by-step instructions rather than performing the action. That correction of the name/title surface is exactly what lets an agent know this is an instructional tool, not a mutating one.

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?

Explicitly gives the two-step workflow: call this to get the steps, then execute with the cotlet_browser_* tools in the Cloud Browser. It also names the official-API alternative and the blocker (credentials only via emailing Club OS support). It does not say when a sibling like configure_follow_up_schedules_scripts_and_segments would be preferred, so 4 rather than 5.

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