Skip to main content
Glama

Club OS by Cotlet

Open the browser

cotlet_browser_open
Read-only

Starts the user's Cloud Browser (a real Chrome on Cotlet, where the user is signed in to their sites) and opens url. Call it first. The URL goes to the site's open tab, else to a new tab, so the user's own tabs stay. Answers the page after it: the elements and text in view, with the same numbers. In Club OS it serves 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_browser_open"
  }
}

Input Schema

NameRequiredDescriptionDefault
appNoLeave it out: the step runs in the user's web browser. Only when cotlet_app_guide names an app's own Cloud Browser, that app's slug, e.g. milanote.
urlNoA public http or https address, e.g. https://example.com.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly/openWorld/destructive=false, so the safety profile is covered; the description adds genuinely useful behavior beyond that: a real signed-in Chrome, tab-reuse semantics that preserve the user's own tabs, and the fact that the call returns the page's visible elements and text with the same numbering. It does not cover latency or what happens if the browser fails to start, but the added context is substantial.

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 three sentences are tight and front-loaded, but they are followed by an ~80-item catalog of Club OS actions that is bulk boilerplate, not tool-specific information an agent needs to open a browser. That dump dwarfs the actionable content and duplicates what the sibling club_os_* tools already advertise.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 2-parameter tool with full schema coverage and strong annotations, the description supplies everything missing: prerequisite ordering ('call it first'), the signed-in browser context, tab targeting behavior, and a summary of the return payload in lieu of an output schema. Nothing an agent needs 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.

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description earns an increment by explaining what the `url` value does at runtime — routed to the site's open tab, otherwise a new tab. The `app` parameter is left to the schema, which is acceptable since its description points at cotlet_app_guide.

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?

States a specific verb and resource ('Starts the user's Cloud Browser ... and opens `url`'), plus a distinguishing scope note that the URL lands in the site's existing tab rather than spawning a duplicate. That separates it from cotlet_browser_navigate and cotlet_browser_tabs without requiring the schema.

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?

'Call it first' gives explicit ordering guidance relative to the rest of the browser toolchain, which is the key selection signal here. It stops short of naming a concrete alternative (e.g. navigate for an already-open browser), so it is clear context but not full when/when-not routing.

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