Skip to main content
Glama

Club OS by Cotlet

Process retail pos sale in Club OS

club_os_process_retail_pos_sale
Read-onlyIdempotent

Process retail pos sale 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_process_retail_pos_sale"
  }
}

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, idempotent, non-destructive and closed-world; the description reinforces this with 'opens nothing by itself' and explains the return content (procedural steps). It also adds a real-world constraint the annotations cannot convey: official API credentials come only via support email. It doesn't state whether any account data is read or how fresh the steps are.

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?

Three sentences, front-loaded with purpose and the critical 'returns how-to, opens nothing' clarification before the follow-up tooling note. The closing API-credentials sentence is somewhat tangential but earns its place by explaining why the browser route is required.

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 definition covers what it returns, what it does not do, and which tools to chain afterward. The remaining gap is minor: it doesn't describe the shape or granularity of the returned steps beyond 'screens, buttons, fields'.

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 no parameters, so the baseline is 4; the description correctly implies a parameterless invocation by framing the tool as returning generic procedure for a named task. No parameter-level meaning is missing.

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 opening sentence restates the title ('Process retail pos sale'), but the second sentence disambiguates the real capability: it returns step-by-step instructions (screens, buttons, fields) rather than performing the sale. That distinction is specific enough to separate it from action-performing siblings, though the leading verb 'Process' still implies execution and could mislead at a glance.

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 lays out an explicit workflow: call this to get the steps, then execute with the cotlet_browser_* tools in the user's Cloud Browser. It also rules out the official API route for this task because credentials require emailing support. It stops short of naming when-not-to-use conditions or sibling alternatives for related POS actions.

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