Skip to main content
Glama

Club OS by Cotlet

Sell a PT package (training agreement) in Club OS

club_os_sell_a_pt_package_training_agreement
Read-onlyIdempotent

Sell a PT package (training agreement) 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_sell_a_pt_package_training_agreement"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

The annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, and the description reinforces this non-obviously with 'opens nothing by itself', heading off an agent's assumption that calling it performs the sale. It also discloses the return shape (step-by-step screens/buttons/fields) and the API credential constraint. It doesn't cover failure modes, such as what happens if the user is not signed in or the package doesn't exist.

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 'opens nothing by itself' caveat are front-loaded, which is exactly right. The trailing official-API sentence is contextually useful but slightly tangential to invoking this specific tool and adds bulk to an otherwise tight definition.

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 input parameters and no output schema, the description carries the burden and does so by describing what comes back (step-by-step screens, buttons, fields) and how to act on it with browser tools. It is nearly complete; only error or precondition handling is left unstated.

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 no parameter meaning to add and the baseline of 4 applies. The description adds no contradictory parameter hints.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb and resource ('Sell a PT package (training agreement)') and immediately clarifies that the tool does not perform the sale but 'Returns how to do it in Club OS step by step (screens, buttons, fields)'. That distinction separates it from sibling mutation tools such as club_os_rewrite_a_package_agreement, which an agent could otherwise confuse it with.

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 explicit next-step routing: use this to get the procedure, 'then do it with the cotlet_browser_* tools in the user's Club OS Cloud Browser'. It also explains why the browser path is required (official API credentials only via support email). It does not state when-not-to-use relative to other Club OS agreement tools, so it stops short of a 5.

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