Skip to main content
Glama

Club OS by Cotlet

Run Prospecting Scorecard in Club OS

club_os_run_prospecting_scorecard
Read-onlyIdempotent

Run Prospecting Scorecard 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_prospecting_scorecard"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Beyond the annotations (readOnlyHint, destructiveHint=false, openWorldHint=false), the description explicitly states that it "opens nothing by itself" and that its output is procedural steps rather than account data, which tells the agent exactly what class of result to expect. It also discloses the credential constraint for the official API route. It stops short of saying whether the guidance is static or tailored to the user's actual account configuration.

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 key caveat (returns instructions, opens nothing) are front-loaded in the first two sentences, which is well structured. The trailing sentence about Club OS's official API is somewhat tangential and padded with a check date, but it is at least relevant decision context for the agent rather than filler.

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 no parameters, no output schema and full annotation coverage, the description supplies what the annotations cannot: what the return value looks like and what the agent should do next. The only real gap is not describing what the scorecard measures or reporting what the guide assumes about the user's setup.

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 the schema carries no semantic burden and the baseline is 4. Nothing in the description is needed to explain inputs, and it correctly does not invent any.

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 ("Run Prospecting Scorecard") and then clarifies the real deliverable: a step-by-step guide of screens, buttons and fields rather than an execution. That clarification rescues what would otherwise be a misleading verb, since the tool name implies execution. It does not, however, explain what the Prospecting Scorecard itself contains or how it differs from sibling report tools like club_os_run_new_prospect_report.

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?

It implies a workflow: get the steps here, then carry them out with the cotlet_browser_* tools in the Cloud Browser. That is useful implied guidance, but there is no explicit when-not-to-use and no routing against the many sibling report tools that return data directly. The API note hints at an alternative access route without saying when an agent should prefer 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