Skip to main content
Glama

Club OS by Cotlet

Run Employee Active Client Report in Club OS

club_os_run_employee_active_client_report
Read-onlyIdempotent

Run Employee Active Client 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_employee_active_client_report"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Beyond the annotations (readOnly/idempotent/non-destructive), it discloses the key behavioral fact that the tool 'opens nothing by itself' and only returns procedural guidance, which prevents an agent from assuming the report was run. It also notes no official API is available without emailing Club OS support, explaining why the browser hand-off is required. It does not describe the shape of the returned instructions (length, format).

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core purpose and the browser hand-off are front-loaded and useful. However, the trailing paragraph on Club OS's official API and support-email onboarding is long, tangential to invoking this tool, and carries an odd dated stamp, which dilutes focus.

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 tool, the description covers what is returned (step-by-step instructions) and what to do next (cotlet_browser_*). The main remaining gap is any hint about the report's content or how many steps to expect, but nothing essential for correct invocation 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 nothing for the description to disambiguate; the baseline applies. No misleading parameter claims are made.

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 pairs a specific verb ('Run') with a specific artifact ('Employee Active Client Report') and scopes it to 'the user's own Club OS account.' It also clarifies that the tool doesn't itself produce the report but returns step-by-step instructions. It doesn't explicitly contrast with the many sibling report tools (commission, lead source, vitals), but the resource name is distinctive enough to select it.

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 a clear two-stage workflow: call this to get the screens/buttons/fields, then execute with the cotlet_browser_* tools in the Cloud Browser. This tells an agent exactly where this tool fits. It stops short of stating when NOT to use it or naming a non-browser alternative.

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