Skip to main content
Glama

Club OS by Cotlet

Copy follow-up segments between locations in Club OS

club_os_copy_follow_up_segments_between_locations
Read-onlyIdempotent

Copy follow-up segments between locations 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_copy_follow_up_segments_between_locations"
  }
}

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 and destructiveHint=false; the description adds the important non-obvious trait that this tool returns instructions rather than executing anything, and that execution is delegated to browser tools. The API-credential note adds useful context on why direct API access isn't an option, though return format details remain thin.

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 message is front-loaded, but the single run-on sentence bundles the action, the returned artifact, the browser delegation, and an extended parenthetical about Club OS's official API. The API paragraph is relevant background yet disproportionately long for a zero-parameter 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?

For a parameterless tool with no output schema, the description covers what it produces (screens, buttons, fields in step-by-step form) and the follow-on workflow. Nothing critical is missing, though a brief statement of what the returned steps assume (e.g., location context) would round it out.

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 applies and there is nothing the description needs to clarify 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?

States a specific verb and resource ('Copy follow-up segments between locations') plus the scope restriction 'in the user's own Club OS account', so the agent knows exactly what operation this covers. It stops short of naming a sibling it should be preferred over or distinguished from, which keeps it below a 5.

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?

Explains the usage pattern clearly: it returns step-by-step instructions and 'opens nothing by itself', after which the agent must use cotlet_browser_* tools in the Cloud Browser. It does not state when-not-to-use or contrast with related follow-up tools such as configuring schedules/scripts/segments, leaving some inference to the agent.

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