Skip to main content
Glama

Club OS by Cotlet

Send workout to members in Club OS

club_os_send_workout_to_members
Read-onlyIdempotent

Send workout to members 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_send_workout_to_members"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

With readOnlyHint=true and idempotentHint=true already declared, the annotations cover the safety profile; the description usefully confirms it 'opens nothing by itself' and describes the return content (step-by-step screens, buttons, fields). It adds some value but leaves the actual response shape and any preconditions (e.g., needing an authenticated Cloud Browser session) unexplained.

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 workflow is front-loaded and clear, but the trailing paragraph about Club OS's official API and emailing support for credentials is tangential to what this tool does and dilutes focus. Trimming it would make the definition sharper without losing anything an agent needs to invoke the 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?

There is no output schema, so the description carries the burden of explaining returns — and it does, stating the response is step-by-step instructions covering screens, buttons, and fields. Combined with the handoff to cotlet_browser_* tools, an agent has enough to call it correctly, though session/prerequisite details are absent.

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 per the baseline this scores 4. There is nothing for the description to disambiguate, and it correctly implies the call is parameterless by describing it as account-scoped guidance.

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 names a specific verb and resource ('Send workout to members in the user's own Club OS account') and then crucially reframes what the tool actually does — it returns step-by-step instructions rather than performing the send. That reframing is what keeps an agent from mistaking it for an action tool, though it does not explicitly differentiate itself from the many other club_os_send_* siblings.

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 usage pattern: call this to get the screens/buttons/fields, then execute with the cotlet_browser_* tools in the Club OS Cloud Browser. The sequencing constraint ('opens nothing by itself') is explicit. It stops short of stating when-not to use it or naming a sibling 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