Skip to main content
Glama

Club OS by Cotlet

Schedule general crm reports in Club OS

club_os_schedule_general_crm_reports
Read-onlyIdempotent

Schedule general crm reports 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_general_crm_reports"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so safety is covered structurally. The description reinforces this with "opens nothing by itself" and clarifies the return is a step-by-step procedure (screens, buttons, fields) plus an API-access note, which is useful added context. However, it does not describe output format or length, so it adds moderate rather than rich behavioral detail beyond annotations.

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 key constraint (returns instructions, opens nothing) is front-loaded and useful, but the description is padded with "from ChatGPT, Claude or any AI agent" and a trailing official-API/credentials aside that is only tangentially relevant to invoking this tool. It is readable but not tightly edited.

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 zero parameters, no output schema, and a read-only annotation profile, the description supplies what an agent needs: what it returns, that it performs no action, and which tools complete the workflow. The only minor gap is not describing the shape or size of the returned instructions.

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 no per-parameter semantics are needed and the baseline of 4 applies. The description correctly implies a parameterless call by framing the tool as an instruction-retrieval step.

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 states a specific verb and resource ("Schedule general crm reports in the user's own Club OS account") and adds the crucial clarification that it only returns step-by-step instructions rather than performing the action. It does not explicitly contrast with the many sibling club_os_* action tools, relying instead on the generic mention of cotlet_browser_* tools, so it stops short of full sibling differentiation.

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 operational guidance: this tool returns how-to instructions and "opens nothing by itself; then do it with the cotlet_browser_* tools in the user's Club OS Cloud Browser." That sequencing tells the agent when to use it and what to do next, though it offers no explicit exclusions for when not to use it.

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