Skip to main content
Glama

Club OS by Cotlet

Reschedule follow-ups from User Search in Club OS

club_os_reschedule_follow_ups_from_user_search
Read-onlyIdempotent

Reschedule follow-ups from User Search 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_reschedule_follow_ups_from_user_search"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/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 goes further by explaining that the tool returns a step-by-step guide (screens, buttons, fields) and 'opens nothing by itself', which is essential and non-obvious behavior. It also discloses that the official API path requires emailing support for credentials, clarifying why the browser automation 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.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Core behavior is front-loaded and clear, but the closing sentence about Club OS's official API sits oddly as a reference note and does not help an agent select or invoke this tool. Phrases like 'from ChatGPT, Claude or any AI agent' are filler relative to the tool's actual job.

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, read-only guide tool, the description covers what is returned, that nothing is mutated, and how the action is actually completed via the browser tools. What is missing is sibling differentiation against other follow-up and reschedule tools.

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 there is nothing the description needs to disambiguate; baseline is 4. The description correctly implies all targeting is derived from the subsequent browser workflow rather than from 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 combination: reschedule follow-ups scoped to 'from User Search' in the user's own Club OS account. It is clearly distinguishable from transitive-workflow siblings such as club_os_transfer_assigned_follow_ups_in_bulk and from the calendar-event sibling, though it never names those alternatives explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description establishes the context of use (user's own account, invoked from an AI agent) and tells the agent what to do afterwards with cotlet_browser_* tools. However, it gives no exclusion criteria or guidance on when to pick this over related siblings like edit_or_reschedule_a_calendar_event, so the agent must infer the boundary.

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