Skip to main content
Glama

Club OS by Cotlet

Bulk edit mms scheduler events in Club OS

club_os_bulk_edit_mms_scheduler_events
Read-onlyIdempotent

Bulk edit mms scheduler 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_bulk_edit_mms_scheduler_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 and destructiveHint=false; the description corroborates and adds the crucial fact that the tool "opens nothing by itself" and only returns screens/buttons/fields. That is the single most important behavioral trait for an agent here, and it goes beyond what the annotations alone convey. It does not say how the returned steps are structured or whether the browser handoff needs a session.

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?

Front-loaded with the action and the key non-action caveat in the first two sentences. The trailing official-API sentence is longer than it needs to be but carries decision-relevant information about credential acquisition.

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 guidance tool with no output schema, it covers what is returned (screens, buttons, fields), what is not done (nothing opened), and which tools complete the task. Minor gaps remain: no mention of how many events can be bulk-edited, how they are selected, or any prerequisites in the Club OS account.

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. The description correctly implies all targeting happens through the returned instructions and the downstream browser tools rather than through arguments.

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 ("Bulk edit mms scheduler events") and explicitly frames the output as step-by-step instructions rather than an action. It is distinguishable from sibling edit tools like club_os_edit_or_reschedule_a_calendar_event by its bulk scope, though it never names a sibling and leaves "mms" undefined.

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?

Clearly routes the agent: this tool gives the Club OS steps, then the actual work is done with the cotlet_browser_* tools in the Cloud Browser. It also flags the official-API alternative and the blocker (credentials only via support email), which is genuine when-to-use context, but there is no explicit exclusion or selection rule among the many sibling tools.

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