Skip to main content
Glama

Exercise.com 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 Exercise.com it covers 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_app_guide"
  }
}

Input Schema

NameRequiredDescriptionDefault
appNoThe app's name or Cotlet slug. Default: Exercise.com.
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?

The annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, so safety is covered. The description adds genuinely new behavior: it is free, opens no browser session, and must precede the first browser action — all useful planning facts. It does not describe the shape of the returned guide beyond listing topic areas.

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 well-structured and front-loaded, but the remaining bulk is a several-hundred-word enumeration of Exercise.com actions that largely duplicates the sibling tool names one-for-one. That catalog does not help an agent decide to call this tool and buries the operational essentials.

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-optional-parameter, read-only guide tool, the essentials are all present: what it returns, the default app, when to invoke it, that it costs nothing and opens no session, and fallback behavior for uncatalogued apps. There is no output schema, and the description adequately sketches the return content, though not its structure.

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 both parameters are documented in-schema, including the Exercise.com default, so the baseline is 3. The description corroborates that the app parameter governs catalog-specific versus general method, but adds no format or syntax detail beyond the schema.

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 states a specific resource and mechanism: it returns guidance on how to operate an app via Cotlet's Cloud Browser tools, including which browser to use, the sign-in link, step-by-step method, screens/menus/actions, notes, and dedicated tools. That distinguishes it from the cotlet_browser_* action tools it precedes. The long Exercise.com catalog adds scope but blurs the core purpose rather than sharpening it.

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 timing rule: 'Call it before the first browser step in an app,' plus coverage guidance that any web app works and apps outside the catalog fall back to the general method. Missing is a when-not clause (e.g., skip it for follow-up steps in a session already covered), which is the only real gap.

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