Skip to main content
Glama

Club OS by Cotlet

Run Opt-Out Report in Club OS

club_os_run_opt_out_report
Read-onlyIdempotent

Run Opt-Out Report 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_run_opt_out_report"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Beyond the readOnlyHint/idempotentHint annotations, it discloses the non-obvious behavior that matters most: nothing is opened or executed by this call and it only returns procedural guidance, with the actual action requiring a separate browser toolset. It also flags an external dependency (API credentials only via support email), which the agent could not infer from 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 core behavior (returns instructions, opens nothing, delegate to browser tools) is front-loaded and well structured with semicolons. The trailing sentence about the official API is longer than necessary and reads like boilerplate shared across the club_os family, but it does carry decision-relevant information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-parameter, read-only tool with no output schema, the description covers what it returns (step-by-step screens/buttons/fields), what it does not do, and the correct next step. There is no meaningful gap left for an agent to fill in before calling it.

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 is an empty object, so there are no parameters whose meaning needs explaining. Baseline 4 applies; the description adds no parameter detail because none is needed.

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 (run the Opt-Out Report) and, crucially, clarifies that the tool returns step-by-step instructions rather than the report data itself, which distinguishes it from a naive reading of the name. It is slightly at odds with its own name ('Run' vs. 'returns how to do it'), but the scope is still clear enough to act on.

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 explicitly states the workflow: call this first to get the screens/buttons/fields, then execute with the cotlet_browser_* tools in the user's Cloud Browser. It also notes the official-API alternative is gated behind an email to Club OS support, which helps the agent rule that path out without asking. No explicit when-not-to-use versus sibling reports, but the report name does the differentiation.

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