Skip to main content
Glama

Club OS by Cotlet

Manage inventory purchase orders in Club OS

club_os_manage_inventory_purchase_orders
Read-onlyIdempotent

Manage inventory purchase orders 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_manage_inventory_purchase_orders"
  }
}

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 readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so safety is covered. The description still adds meaningful context beyond them: it discloses that the tool only returns instructions (screens, buttons, fields), performs no action, and explains the Club OS API credential constraint that forces the browser path.

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?

Purpose and the read-only/next-step behavior are front-loaded, and the API note genuinely explains why browser automation is required. Minor padding in 'from ChatGPT, Claude or any AI agent' and some repetition of the title in the opening clause.

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 guidance tool, the description is nearly complete: what it returns, that it has no side effects, what to call next, and the API alternative's limitation. It does not say how much task context the agent should supply (e.g. which purchase order) for the returned steps to be relevant, a small 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, which sets the baseline at 4. Nothing is needed to disambiguate inputs, and the description does not confuse matters with parameter talk.

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 (manage inventory purchase orders in Club OS) and then clarifies the actual behavior: it returns step-by-step instructions rather than performing the action. That correction of the 'manage' verb is valuable, though it never names the closest siblings (e.g. club_os_create_inventory_item, club_os_run_all_inventory_report) to sharpen the boundary.

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 lays out the intended workflow: this tool returns the Club OS steps and 'opens nothing by itself', then execution happens via the cotlet_browser_* tools in the Cloud Browser. That is clear when/how guidance, but it gives no exclusions or guidance on when a direct action tool should be preferred over this guidance-then-browse pattern.

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