Skip to main content
Glama

Club OS by Cotlet

Send a test campaign email in Club OS

club_os_send_a_test_campaign_email
Read-onlyIdempotent

Send a test campaign email 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_send_a_test_campaign_email"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, and the description adds genuinely new context: the call performs no action, returns screen/button/field-level instructions, and requires a separate browser tool to execute. That is substantive behavioral disclosure beyond the annotations, though it says nothing about response size or limits.

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 purpose and the 'opens nothing by itself' qualifier are front-loaded where they matter most. The phrase 'from ChatGPT, Claude or any AI agent' is filler, and the API note, while relevant context, is somewhat lengthy for its value.

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 rich annotations, the definition covers what remains: the tool returns guidance rather than acting, and the real action happens via cotlet_browser_* tools. The note on the official API explains why the browser route is needed, leaving little ambiguity for an agent.

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 no parameters, so there is no parameter semantics to explain and the baseline applies. The description's framing of what the parameterless call yields is helpful in place of param documentation.

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 action and object (send a test campaign email) and, importantly, corrects the implication of the tool name by stating it only returns step-by-step instructions and opens nothing itself. It does not explicitly name a sibling test-vs-live campaign tool, so it stops short of full 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 clearly frames the use case (a test campaign email in the user's own account) and states the follow-up path: perform the action with cotlet_browser_* tools in the Cloud Browser. It does not explicitly say when NOT to use this versus the other campaign-sending siblings, so it is clear context without exclusions.

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