Skip to main content
Glama

Club OS by Cotlet

Run Commission Report in Club OS

club_os_run_commission_report
Read-onlyIdempotent

Run Commission 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_commission_report"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true and openWorldHint=false, so the safety profile is largely covered. The description does add genuinely useful behavior beyond that: it "opens nothing by itself" and returns procedural guidance (screens, buttons, fields), plus the caveat about API credentials. Credit is warranted, but return format details and any preconditions for the Cloud Browser step are left implicit.

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 behavior and handoff to cotlet_browser_* tools is front-loaded and clear. The closing paragraph on Club OS's official API, complete with a "checked 11 Nov 2026" timestamp, is tangential justification that dilutes the definition and could be trimmed to a clause.

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 annotations covering safety, the description supplies what an agent still needs: what it returns (step-by-step instructions), that it performs no action itself, and which tool family completes the task. The main remaining gap is that it does not say what to do when the Cloud Browser session is unavailable or unauthenticated.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/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 parameter meaning for the description to add; the baseline for a parameterless tool applies. However, the description never addresses how report scope (e.g. date range, employee) is specified given that no inputs exist, which is a real semantic gap for a report tool.

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 Commission Report in the user's own Club OS account") and clarifies the non-obvious nature of the action: it returns step-by-step instructions rather than executing the report. It differentiates by report type from the many sibling report tools by name convention only, without an explicit sibling callout, so it stops 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?

Gives clear usage context and an explicit two-step workflow: call this first to get the Club OS screens/buttons/fields, then act via the cotlet_browser_* tools in the user's Cloud Browser. It also explains why the official API is not the route (credentials only via emailing support). It lacks explicit when-not-to-use conditions or a named alternative for users who already have API credentials.

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