Skip to main content
Glama

Club OS by Cotlet

Run all inventory report in Club OS

club_os_run_all_inventory_report
Read-onlyIdempotent

Run all inventory 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_all_inventory_report"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations declare readOnly and idempotent, but the description adds critical behavior they cannot convey: the call returns procedural guidance rather than data, performs no browser action on its own, and mandates a follow-up step with cotlet_browser_* tools. It also discloses an external constraint (API credentials only via support email). What's missing is any indication of the shape or granularity of the returned steps.

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 essential scoping and hand-off information is front-loaded, but the second sentence is a tangled run-on ('Returns how to do it ... and opens nothing by itself; then do it with ...'). The closing API paragraph is tangential to invoking this specific tool and could be trimmed without harming selection.

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 read-only annotations, the description covers what an agent needs: what it returns, that it is non-acting, and which tools to chain next. Only the form of the returned instructions (length, structure, copy-pasteability) is left unspecified.

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?

There are zero parameters, so the baseline applies; the description correctly implies no input is needed. No parameter meaning is required or omitted.

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 the specific resource ('all inventory report') and clarifies the actual output: step-by-step guidance on screens, buttons and fields in Club OS. This distinguishes it from sibling report tools by resource, though it doesn't explicitly contrast with them by name. The opening verb 'Run' is slightly misleading until the second sentence corrects it.

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 workflow context: this tool only returns instructions and 'opens nothing by itself', after which the agent should act via the cotlet_browser_* tools in the user's Cloud Browser. It also notes the official-API path requires emailing support for credentials, useful for choosing an approach. No explicit exclusions against the sibling report tools, but the operating context is unambiguous.

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