Skip to main content
Glama

Club OS by Cotlet

Configure kpi goals in Club OS

club_os_configure_kpi_goals
Read-onlyIdempotent

Configure kpi goals 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_configure_kpi_goals"
  }
}

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?

Annotations already declare readOnlyHint=true, openWorldHint=false, idempotentHint=true, destructiveHint=false, so the safety bar is lower. The description still adds real value beyond them: it discloses that the tool 'opens nothing by itself', that the return value is a step-by-step procedure, and that actual execution is delegated to browser tools. It does not describe the exact shape or granularity of the returned steps.

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 opening sentence and the 'opens nothing by itself' clause are front-loaded and earn their place. The closing official-API sentence is a long, loosely punctuated digression that restates 'Club OS has an official API' twice and adds a dated credential note of marginal relevance to invoking this tool.

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 guidance tool, the description supplies what an agent actually needs: what gets returned (ordered steps), that nothing is mutated, and which tool family performs the real work. Only the follow-on browser step lacks concrete detail (which cotlet_browser_* tool to start with).

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. There is no parameter meaning to add and the description does not need to compensate for any schema gaps.

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 resource (KPI goals in Club OS) and, critically, clarifies that the tool does not perform the action itself but returns step-by-step instructions (screens, buttons, fields). This resolves the mismatch between the imperative name/title and the read-only behavior. It does not explicitly differentiate itself from the many sibling club_os_configure_* tools, which keeps it from 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: call this to get instructions, then execute with the cotlet_browser_* tools in the user's Club OS Cloud Browser. The API note further explains why the browser path is needed rather than direct API calls. No explicit when-not or sibling comparisons, but the workflow routing is unambiguous.

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