Skip to main content
Glama

Club OS by Cotlet

Run Vitals Report in Club OS

club_os_run_vitals_report
Read-onlyIdempotent

Run Vitals 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_vitals_report"
  }
}

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/closed-world/idempotent, but the description adds the crucial non-obvious trait that the tool performs no action and only returns instructions, plus where the actual execution must happen. The API-credentials note further explains why browser automation is needed. Minor omission: no detail on the exact output format beyond 'step by step (screens, buttons, fields)'.

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?

Front-loaded with the action and the key constraint ('opens nothing by itself'), then the follow-up mechanics. The trailing paragraph about Club OS's official API and the support-email credential process is tangential to invoking this tool and consumes significant tokens.

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 output schema, the description carries the burden of describing the return, and it does so adequately ('how to do it in Club OS step by step (screens, buttons, fields)'). Nothing an agent needs to call the tool correctly is missing, though the relationship to the recurring-delivery sibling is never addressed.

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?

Zero parameters, so the schema/Vitals target is not parameterizable; baseline 4 applies. The description adds nothing parameter-related, and the phrase 'in the user's own Club OS account' is slightly at odds with the absence of any account/selector input.

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?

States a specific verb and resource ('Run Vitals Report in the user's own Club OS account') and immediately clarifies it is a guide-returning tool, not an executor ('opens nothing by itself'). It is distinguishable from the many other run_*_report siblings by naming the report type, though it never explicitly contrasts itself with them.

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?

Explicitly describes the intended two-step workflow: call this to get step-by-step screens/buttons/fields, then execute with the cotlet_browser_* tools in the Club OS Cloud Browser. It lacks any when-not-to-use guidance or routing among sibling reports such as schedule_recurring_vitals_report_delivery.

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