Skip to main content
Glama

Club OS by Cotlet

Cotlet: how to work in an app

cotlet_app_guide
Read-onlyIdempotent

How to work in an app by clicking in the user's Cloud Browser with Cotlet's browser tools: which browser to use for this workspace and the sign-in link, the method step by step, the app's screens, menus and actions, notes, and the app's dedicated tools when Cotlet has them. Call it before the first browser step in an app. Works for any web app; one outside Cotlet's catalog gets the general method. Free, no browser session. For Club OS it covers these actions: Run New Prospect Report, Run Lead Source Report, Run Prospecting Scorecard, Run Vitals Report, Schedule recurring Vitals Report delivery, Run Commission Report, Run Unpaid Invoices Report, Run Opt-Out Report, View Text Usage Analytics dashboard, Search users (User Search), View a staff member's calendar from User Search, Add a new lead, Use the Digital Guest Waiver to create a prospect, View and follow up with Re-Interested leads and inactive members, Update a prospect or member profile, Merge duplicate accounts, Find and restore a deleted account, Transfer assigned follow-ups in bulk, Reschedule follow-ups from User Search, Configure follow-up schedules, scripts and segments, Turn on automatic follow-ups, Copy follow-up segments between locations, Manage location settings, defaults, marketing sources and telephone inquiry script, View the calendar, Create a calendar event or appointment, Edit or reschedule a calendar event, Delete or cancel a calendar event, Attach event reminders to events, Schedule public group training events / fitness consultations, Create or edit an email campaign (Blast or Automatic), Send a test campaign email, Send or schedule a blast email campaign, Send an email campaign to a User Search audience, Activate an automatic email campaign, Deactivate an automatic email campaign, View email and text campaign history and analytics, Create a text campaign (draft), Send or schedule a bulk text campaign, Create or edit member services, packages and commission setup, Sell a PT package (training agreement), Change training agreement payment dates, cancellation date, salesperson, or un-expire sessions, Retry charging an unpaid PT invoice, Write off an invoice, Comp an invoice, Refund a PT invoice (Club OS Training Management), Refund a member's previously paid credit, Request a bulk PT invoice write-off, View a member's account, profile, transactions and attendance (Member Management), Enroll, renew or replace a membership (Member Enrollment / Contract Entry), Freeze a member account, Cancel a member account, Add, edit, delete, credit or cancel add-ons and one-time account charges, Take payment for member dues or add-ons (MyPOS), Refund member dues or add-on payments (MMS), Void a POS transaction or return items (MyPOS), Add an employee, Edit a staff member's role, manager type, location access or permissions, Revoke or restore an employee's access, Delete an employee account, Edit employee order on the calendar, Subscribe to / sync the Club OS calendar to other devices, Rewrite a package agreement, Run Employee Active Client Report, Create inventory item, Manage inventory purchase orders, Manage cash drawers, Process retail pos sale, Manage locker assignments, Configure belt programs levels ranks, Manage employee timeclock, Process event check in, Configure membership offers, Configure offer discount codes, Waive mms invoice payment, Configure workout nutrition templates, Send workout to members, Bulk edit mms scheduler events, Add YouTube video to media library, Manage pt agreement freeze, Configure kpi goals, Configure custom user fields, Configure mobile store availability, Configure mobile app branding, Run all inventory report, Run follow up audit report, Schedule general crm reports.

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": "cotlet_app_guide"
  }
}

Input Schema

NameRequiredDescriptionDefault
appNoThe app's name or Cotlet slug. Default: Club OS.
taskNoWhat the user wants done in the app, in their words.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and openWorldHint=false, so safety needs no restating. The description adds genuinely new behavioral context: 'Free, no browser session,' which tells the agent this call costs nothing and does not open or consume a browser session — a distinction that matters next to cotlet_browser_open. It does not describe response size or format beyond naming the content sections.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The first two sentences are well front-loaded and do the real work. The remainder is an ~90-item enumeration of Club OS actions that consumes enormous context without helping the agent decide whether or how to call a 2-parameter tool — that scope belongs in returned content or a resource, not the definition. Volume actively works against the guidance it is attached to.

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 2-optional-parameter tool with no output schema, the description covers the essentials: when to call it, that it works for any web app including uncatalogued ones, that it is free and session-free, and roughly what the returned guide contains. A short note on the shape/size of the returned instructions would close the remaining gap, but nothing needed to invoke it correctly is absent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%: app (name or Cotlet slug, default Club OS) and task (what the user wants, in their words) are both fully documented. The description adds little to either — the long Club OS action list loosely implies what can go in 'task' but never says to pass the user's goal verbatim or how specificity affects the returned guidance. Baseline 3 applies when the schema carries the semantics.

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 names a specific resource (in-app working instructions for the user's Cloud Browser) and enumerates what the guide returns: which browser, the sign-in link, the step-by-step method, screens/menus/actions, notes, and dedicated tools. It is clearly not one of the cotlet_browser_* action tools, since it returns guidance rather than performing a click/fill/navigate. The trailing 90-item Club OS action catalog is scope evidence rather than purpose, and it dilutes the otherwise crisp definition.

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?

Explicit trigger: 'Call it before the first browser step in an app,' which positions it ahead of cotlet_browser_open/click/navigate. It also states the fallback condition — apps outside Cotlet's catalog still get the general method — so the agent knows the tool is never the wrong choice when starting browser work. What's missing is an explicit exclusion (e.g., don't call it again mid-task or for non-browser requests).

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