Skip to main content
Glama

Club OS by Cotlet

Transfer assigned follow-ups in bulk in Club OS

club_os_transfer_assigned_follow_ups_in_bulk
Read-onlyIdempotent

Transfer assigned follow-ups in bulk 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_transfer_assigned_follow_ups_in_bulk"
  }
}

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?

The 'opens nothing by itself' caveat usefully reinforces the readOnlyHint=true and destructiveHint=false annotations by telling the agent no state change occurs. It also discloses the practical constraint that the official API requires credentials via email to Club OS support, which annotations cannot convey; only the exact return payload shape is left implicit.

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 behavior and the browser-tool follow-up are front-loaded well, but the closing sentence about the official API and emailing support is tangential detail that lengthens the definition without directly helping an agent call the tool. It is informative context but not tightly on-task.

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 parameters, no output schema, and annotations already covering safety, the description supplies the missing operational context: that the output is step-by-step UI instructions and that execution happens elsewhere. It is complete enough for an agent to select and use it correctly.

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 input schema has zero parameters, so there is nothing for the description to disambiguate; it correctly implies no inputs are required. Baseline 4 applies for a no-parameter tool.

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 (transfer assigned follow-ups in bulk) and scopes it to the user's own Club OS account, so an agent can tell it apart from sibling follow-up tools like reschedule or copy segments. It stops short of explicitly contrasting with those siblings, but the action is unambiguous.

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 clearly frames the tool as a planning/instruction tool ('returns how to do it step by step ... opens nothing by itself') and names the follow-on path for execution (cotlet_browser_* tools in the Cloud Browser). It does not state exclusions or name any sibling as an alternative, which keeps it below a 5.

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