Skip to main content
Glama

Club OS by Cotlet

Schedule recurring Vitals Report delivery in Club OS

club_os_schedule_recurring_vitals_report_delivery
Read-onlyIdempotent

Schedule recurring Vitals Report delivery 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_schedule_recurring_vitals_report_delivery"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnly, idempotent, non-destructive, non-open-world behavior, and the description reinforces this by stating it 'opens nothing by itself', so there is no contradiction. It also adds genuinely useful context beyond annotations: the follow-up execution path via cotlet_browser_* and the fact that official API credentials require emailing Club OS support. It does not describe the shape of the returned instructions or any limits, keeping it short of a 5.

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 core contract ('returns how to do it, opens nothing by itself') is front-loaded and every clause is functional. The trailing note about Club OS's official API is somewhat tangential and slightly dense in one paragraph, but it materially informs why a browser-based path is needed.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/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 rich annotations, the description supplies everything an agent needs: what it returns, that it performs no side effects, which tools to use afterward, and why the API route is unavailable. Nothing essential to correct invocation is missing.

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 no parameter semantics to explain and the baseline is 4. The description correctly implies all setup details are captured interactively during the guidance flow rather than passed as 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?

The description names a specific verb and resource (schedule recurring Vitals Report delivery) and clarifies the unusual contract: it returns step-by-step instructions for Club OS rather than performing the action. It could more directly separate itself from the sibling club_os_run_vitals_report, which is never named, so an agent must infer that one runs a report and this one sets up recurring delivery.

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 gives clear operative guidance: call this to get the click-by-click path, then actually perform it with the cotlet_browser_* tools in the user's Club OS Cloud Browser. What is missing is an explicit when-not or a named alternative (e.g., the run-report or schedule-general-crm-reports siblings), leaving the agent to infer selection criteria.

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