Skip to main content
Glama

Club OS by Cotlet

Run New Prospect Report in Club OS

club_os_run_new_prospect_report
Read-onlyIdempotent

Run New Prospect Report 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_run_new_prospect_report"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already cover readOnlyHint, idempotentHint and destructiveHint: false, so the safety profile is known. The description usefully confirms the behavior ('opens nothing by itself') and discloses an external constraint — Club OS API credentials require emailing support — which explains why browser automation is needed. Beyond that it adds little about what the returned instructions look like in practice or what happens if the account lacks the report.

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 critical clarification (returns instructions, opens nothing) is front-loaded in the first two sentences. The trailing API paragraph is longer than it needs to be for the value it delivers, and the phrase 'from ChatGPT, Claude or any AI agent' is filler, but overall nothing is badly misplaced.

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 tool with full annotation coverage, the description covers what it returns, that it performs no action, and the follow-up tool family to invoke. It is nearly complete; a line about prerequisites (e.g., an active Cloud Browser session) would close the remaining gap.

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 schema-level for the description to compensate for; the baseline of 4 applies. The description correctly implies no inputs are needed beyond the user's own Club OS account context.

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 makes clear that despite the 'Run' verb in the name, this tool does not execute anything: it 'Returns how to do it in Club OS step by step (screens, buttons, fields) and opens nothing by itself.' That resolves the main ambiguity. It does not explicitly differentiate itself from the many sibling report tools (lead source, follow-up audit, etc.), so an agent must infer differentiation from the report name alone.

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?

Clear usage context is given: call this first for the guidance, then 'do it with the cotlet_browser_* tools in the user's Club OS Cloud Browser.' That prescribes a concrete two-step workflow. It stops short of explicit when-not-to-use guidance or naming an alternative sibling, and the official-API note is informative but doesn't state what to do if API credentials already exist.

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