Skip to main content
Glama

Club OS by Cotlet

Attach event reminders to events in Club OS

club_os_attach_event_reminders_to_events
Read-onlyIdempotent

Attach event reminders to events 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_attach_event_reminders_to_events"
  }
}

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 declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so safety is covered. The description adds genuinely non-obvious behavior: the tool opens nothing by itself and returns screens/buttons/fields instructions, meaning the actual side effect happens in a separate browser session. The parenthetical about Club OS requiring an email to support for API credentials explains why the browser route exists.

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?

The operative constraint (returns steps, opens nothing, then use the browser tools) is front-loaded in the first two sentences. The trailing official-API sentence is much longer than it needs to be and carries a stray date stamp, but it does justify why the browser workflow is necessary rather than being pure filler.

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 definition tells the agent what comes back (step-by-step screens, buttons, fields) and what to do next. The only soft gap is that prerequisites for the Cloud Browser session (auth, availability) are implied by the cotlet_browser_* reference rather than stated.

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 schema has zero properties and additionalProperties=false, so there are no parameters whose meaning needs elaboration. Baseline for a parameterless tool is 4, and nothing in the description creates ambiguity about inputs.

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 first sentence pairs a specific verb and resource ("Attach event reminders to events") with the scope "in the user's own Club OS account," and then immediately clarifies that the tool actually returns step-by-step instructions rather than performing the change. That correction is essential because the tool name implies a mutation. It stops short of naming any of the club_os_* siblings to differentiate against, which keeps it out of 5 territory.

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 states the context of use (from ChatGPT, Claude or any AI agent) and, more importantly, the workflow: call this, then execute the steps with the cotlet_browser_* tools in the Cloud Browser. That routing to an alternative tool family is the exact guidance an agent needs. It does not state any case where this tool should be skipped, so no explicit exclusions.

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