Skip to main content
Glama

Club OS by Cotlet

Run follow up audit report in Club OS

club_os_run_follow_up_audit_report
Read-onlyIdempotent

Run follow up audit 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_follow_up_audit_report"
  }
}

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?

Annotations already establish readOnly, idempotent, non-destructive and closed-world behavior, and the description reinforces rather than contradicts them with "opens nothing by itself." It adds genuine context the annotations cannot convey: the return payload is procedural guidance, and the actual execution happens in the user's own Club OS Cloud Browser via cotlet_browser_* tools. The note about the official API requiring an email to Club OS support explains why the browser path exists, which is useful but sits adjacent to the core behavior.

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?

Purpose and the critical "returns steps, opens nothing" caveat are front-loaded, and the follow-up workflow sentence follows logically. The closing API sentence is the weakest part: it is long and tangential to invoking this tool, though it does justify the browser-based approach.

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 zero parameters, no output schema and rich annotations, an agent has enough to call this correctly and knows what to do with the result. The only mild gap is that the description does not characterize the shape of the returned steps beyond "screens, buttons, fields".

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 the baseline is 4 and there is nothing to disambiguate. The description implicitly confirms this by describing a fixed report with no options or filters to specify.

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?

States a specific verb and resource ("Run follow up audit report") and immediately clarifies a non-obvious twist: it returns step-by-step instructions rather than data. That distinguishes it from data-returning siblings like club_os_run_lead_source_report, though it does not name or contrast any sibling explicitly.

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?

Gives a clear two-step workflow: call this to get screens/buttons/fields, then execute with cotlet_browser_* tools in the user's Cloud Browser. The "opens nothing by itself" line prevents an agent from assuming the report is produced. It stops short of stating when this is preferable to other follow-up tools such as the bulk transfer or segment configuration siblings.

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