Skip to main content
Glama

Club OS by Cotlet

Manage cash drawers in Club OS

club_os_manage_cash_drawers
Read-onlyIdempotent

Manage cash drawers 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_cash_drawers"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Adds genuinely useful, non-obvious behavior beyond annotations: the tool returns step-by-step instructions and "opens nothing by itself," which is consistent with readOnlyHint=true. However, the trailing paragraph about Club OS's official API and credentials is tangential and does not describe the cash-drawer behavior itself. The description does not state the exact return shape, leaving gaps.

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 core sentences are front-loaded and efficient, but the final paragraph about the official API and credential setup is mostly irrelevant to managing cash drawers, padding the definition without adding actionable value. Structure is reasonable but the content is not tightly scoped.

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, read-only guidance tool with annotations covering safety, the description does enough: it explains the return (step-by-step screens, buttons, fields) and the follow-up workflow with browser tools. The absence of an output schema means explaining the return format is important, and it does so adequately if briefly.

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 the schema is complete by default and the baseline is 4. Nothing in the description is needed to clarify parameters, and it does not attempt to.

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 cash drawers") and clarifies its actual behavior: it "Returns how to do it in Club OS step by step (screens, buttons, fields) and opens nothing by itself." It distinguishes itself from sibling operations by naming the resource and pointing to the cotlet_browser_* tools for execution, though it never contrasts with other club_os_manage_* siblings.

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?

Gives a clear workflow: call this to get the step-by-step instructions, then actually perform the action with the cotlet_browser_* tools in the Club OS Cloud Browser. This routes the agent to an explicit alternative for execution. It lacks explicit when-not-to-use guidance versus other manage tools, keeping it at 4.

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