Skip to main content
Glama

Exercise.com 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 Exercise.com it serves these actions: Add or invite a new client, Delete a pending client invitation, Delete a client, Invite a lead to sign up as a client, Link a completed lead assessment to an existing client account, View client visit records and run visit reports, View a client's activity event log, View a client's exercise history while building a workout, Edit a client's logged workout, Log a workout on behalf of a client, Create a new workout plan, Copy a workout plan on the Trainer Dashboard, Publish a workout plan and sync changes to all users, Publish a workout plan to a group (optionally on a launch date), Assign or start a workout plan for a client, Put a workout plan up for sale, Get the direct link for a workout plan, Create and edit an assessment (fields, scoring formulas, rules), Publish an assessment for clients, Send or assign an assessment to a client, multiple clients or a group, Fill out an assessment on a client's behalf, Create or edit a group, Post or schedule a message in a group Discussion, Reschedule a session from the Appointments tab, Cancel a session / appointment, Process a no-show or late cancel, with or without a fee, View My Sessions (client view of upcoming and completed sessions), Check in a client (front desk, kiosk or barcode), Create, edit and configure packages, Archive, view archived and restore packages, Add or charge a package on a client's account, Backdate a client's subscription, Issue a refund on a charge, View all charges and export a charges report, View Business Dashboard metrics, subscriptions and purchasers, Create products and manage inventory, Ring up in-person sales in Point of Sale / Kiosk, Send a message to a client (Messages), Set up an automatic reply for new incoming messages, Create, pause, organize and delete Automations, Send a new waiver or contract to a client, View signed contracts and waivers, Customize Platform (waiver requirement, emails, public product and package pages, tabs, defaults), Add staff members, set roles and permissions, Connect Stripe, MindBody and wearable or connected apps, Create an API key (paid add-on), Brand the web platform and mobile apps, View and filter the Clients list, Export a client's logged workouts, View the Schedule calendar, Create sessions and events on the Schedule calendar, Create availability schedules and set staff unavailable, Create and manage locations, Create, clone and configure services, Review changes made to services and packages, View and manage client service balances, Review client wearable and connected-app data, Create, rename and arrange dashboards and widgets (Analytics), Generate, filter, print and export reports, Read messages and SMS usage, Create dependents and share packages; book or log in as a dependent, Merge accounts, Create send or charge invoice, Adjust account balance, View client nutrition, Edit client food log, Add habit tracker, Export client measurements, Configure kisi package location access, Initiate instant payout.

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.7/5.0
Behavior3/5

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

The description adds real value beyond the annotations: the session is a real Chrome where the user is already signed in (auth context), user tabs are preserved, and the call returns the visible elements and text that later reads will refer to by the same numbers. However, it says nothing about what happens on failure, whether a new browser instance is spawned per call, or how the non-idempotent behavior manifests.

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 opening three sentences are front-loaded and efficient, but they are followed by a multi-dozen-item enumeration of Exercise.com actions that dwarfs the actual invocation guidance and adds little for deciding how to call this tool. The bulk of the text does not earn its place.

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, no-output-schema browser opener, the description covers prerequisites, tab behavior, and what comes back from the page. The appended action catalog is more app context than tool context, but nothing essential to invoking it correctly is missing.

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 the optional `app` opt-out. The description adds meaning to `url` by explaining tab-targeting (site's open tab, else new tab), but does not otherwise elaborate on formats or constraints beyond the schema.

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 action and resource: it starts the user's Cloud Browser (a real signed-in Chrome on Cotlet) and opens `url`, and adds the ordering cue "Call it first". The signed-in-Chrome detail distinguishes it from a generic fetcher and from the sibling browser_* action tools.

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 an explicit ordering rule relative to the browser siblings, and the tab-targeting sentence explains when an existing tab is reused versus a new one. It stops short of saying when to use cotlet_browser_navigate or cotlet_browser_tabs instead, so it is clear context without explicit exclusions.

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