Skip to main content
Glama

Club OS by Cotlet

Configure membership offers in Club OS

club_os_configure_membership_offers
Read-onlyIdempotent

Configure membership offers 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_membership_offers"
  }
}

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, destructiveHint=false and idempotentHint=true, so the safety profile is covered. The description adds genuinely non-redundant behavior: the tool returns step-by-step UI instructions rather than performing actions, opens nothing, and must be paired with the browser tools to actually apply changes. The note about the official Club OS API requiring an email to support adds useful auth context, though the date stamp "checked 11 Nov 2026" is odd.

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 clarification (returns instructions, opens nothing, then use browser tools) is front-loaded within the first two clauses, which is good. However, that second sentence is overloaded with a semicolon-joined clause chain, and the trailing official-API sentence is tangential for an agent deciding whether to call this tool. It is not bloated, but it is not tight either.

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 no output schema and no parameters, the description carries the return-value burden and does so: it specifies the output is step-by-step guidance covering screens, buttons and fields. Combined with the explicit follow-up path via cotlet_browser_* tools, an agent has enough to call this and know what comes back. Only the ambiguity of whether the result is scoped to a location or account is unaddressed.

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?

There are zero parameters and the schema is fully described, so there is no parameter semantics burden beyond what structured data already provides. Baseline 4 applies; the description neither needs to nor attempts to add parameter meaning.

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?

"Configure membership offers" is a specific verb+resource pair, but on its own it implies the tool performs the configuration. The description immediately corrects this: "Returns how to do it in Club OS step by step (screens, buttons, fields) and opens nothing by itself", so an agent learns this is an instruction-retrieval tool, not a mutating one. The differentiation from the many other club_os_configure_* siblings is only implied by the resource name, not stated.

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?

The description gives a clear usage path: call this first to get the steps, then execute them "with the cotlet_browser_* tools in the user's Club OS Cloud Browser". That is an explicit hand-off to an alternative toolset. What is missing is any when-not guidance (e.g., when to skip this and act directly, or when the official API path is preferable).

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