Skip to main content
Glama

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 Gymdesk it serves these actions: View gym dashboard, Retry an overdue payment or send a payment reminder, View member or visitor profile, Add a note (optionally with a task) to a member profile, Add or quick-add a member or visitor, Edit member profile, Add or adjust a membership on a member profile, Freeze a member, Unfreeze a member, Bulk freeze, cancel or reactivate members, Bulk assign a document to members, Send a bulk text/SMS to members, Send targeted push notification to members or leads, Import members, memberships, attendance, leads or products from CSV, Export member list or documents, Merge duplicate member or lead profiles, Configure member settings, custom fields and portal options, Create and manage member sign-up forms, Create and edit membership options, Create rosters and assign sessions or memberships, Create document and waiver templates, Add or send a document to a member, visitor or lead profile, Check a member, visitor or lead in to a session, Mass check-in members to a session, Add attendance manually, including past dates, View and export attendance reports, Configure attendance settings and membership cards, Run Front Desk Mode, View member growth reporting, View member payment history, recurring payments and invoices, Create a one-time charge for a member, Modify a scheduled membership payment, Cancel future recurring membership payments, Refund a payment, Record a manual (offline) payment, Create and manage discount codes, Configure billing settings, payment processors, taxes and failed-payment retries, View billing overview, daily billing report and billing growth, View the gym schedule and session participants, Edit, cancel or delete a session, Configure booking settings and booking forms, Log skill progress and mark skills as passed, View promotion readiness and progress, Use WODs in Gymdesk, Add, edit and remove managers and instructors and set permissions, Log staff work hours for payroll tracking, View and export the payroll report, View and filter leads, Add a lead manually, Bulk delete, re-status, mark spam or message leads, Send and answer individual or two-way messages, Create, edit and activate marketing automations, View marketing dashboard and acquisition funnel, Configure marketing settings, email content and text messaging, Create a Point-of-Sale sale, View, search and export sales transactions, Refund a sale or cancel a manual sale, Create and manage products, variants, categories and inventory, Create digital gift cards, Enable and configure the online shop, Send shipping updates for online shop orders, Edit website homepage and pages and publish, Manage website lead forms and embeddable widgets, Set up a custom domain and white-label the website, Connect Zoom for virtual sessions, Connect ActiveCampaign, View account plan, View Gymdesk invoices, Add a new location to the account, Migrate settings between locations, View cross-location franchise reports, Connect smoothcomp academy, View competitions and athlete activity, Endorse competition, Register or invite member to competition, Manage referral rewards, View referrals, View and export accounting, View and export payments, View messaging history, Configure custom email domain, Convert or invite lead to member, Send automation webhook.

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

A3.6/5.0
Behavior4/5

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

Beyond the annotations it discloses meaningful behavior: the URL reuses the site's existing tab rather than spawning one, the user's own tabs are preserved, and the call answers with the in-view elements and text using the same numbering. The long Gymdesk action list adds no behavioral information about this tool.

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 four sentences are well front-loaded and earn their place, but they are followed by an enormous enumeration of Gymdesk actions that dominates the text and is unrelated to opening a browser. That list belongs in an app guide, not this tool 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?

For a two-parameter, zero-required, no-output-schema tool, the description covers ordering, tab behavior, session/auth context, and what comes back. The Gymdesk catalog is surplus rather than a missing piece, so the definition is functionally complete.

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%, and the schema already explains both `app` and `url` fully, so the baseline is 3. The description adds only the tab-targeting semantics of `url`; it says nothing new about the `app` escape hatch beyond what the schema states.

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: 'Starts the user's Cloud Browser ... and opens `url`', with clarifying detail that it is a real Chrome where the user is already signed in. It never names the sibling it might be confused with, cotlet_browser_navigate, so differentiation from later navigation is left implicit.

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 all the other browser_* tools, which is the main decision an agent faces. It stops short of stating exclusions, e.g. that a already-open browser should be reused rather than started again, or how it relates to cotlet_browser_navigate.

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