Skip to main content
Glama
Sign In

Gymdesk by Cotlet

by dev.cotlet
OverviewDiscussionsAdmin

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 Gymdesk it covers 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_app_guide"
  }
}

Input Schema

NameRequiredDescriptionDefault
appNoThe app's name or Cotlet slug. Default: Gymdesk.
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=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so safety is covered structurally. The description still adds genuinely useful non-annotation context: it is "Free, no browser session," meaning no Cloud Browser session is consumed or left open, and it explains the fallback behavior for apps outside the catalog. Minor tension exists between "works for any web app" and openWorldHint=false, but the tool itself returns static guidance rather than touching external entities.

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 two sentences are well front-loaded and information-dense, but they are followed by a roughly 90-item Gymdesk action dump that restates the capabilities of the sibling gymdesk_* tools almost one-for-one. That block is essentially catalog duplication inside a description and overwhelms the signal an agent needs to decide whether to call this tool.

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

Completeness3/5

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

For a two-parameter, read-only guidance tool with 100% schema coverage and no output schema, the description covers when to call it, what kind of content it returns, and that it costs nothing and opens no session. However, the usefulness of the return is blurred by the sprawling feature list, and nothing says how specific or generic the returned guidance will be for a given task. Adequate but padded.

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 description coverage is 100%, so both parameters (app, task) are already documented, including the Gymdesk default and the 500-char task limit. The description reinforces intent with "which browser to use for this workspace" and "the app's dedicated tools," but adds no new syntax, format, or constraint detail. Baseline 3 applies when the schema does the heavy lifting.

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?

"How to work in an app by clicking in the user's Cloud Browser with Cotlet's browser tools" states a specific resource (operating guidance for an app) and enumerates the contents: which browser to use, sign-in link, step-by-step method, screens/menus/actions, notes, and app-specific tools. It is clearly differentiated from the mechanical siblings like cotlet_browser_click or cotlet_browser_fill_form. The very long Gymdesk action inventory that follows does not sharpen the purpose further and mostly dilutes 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?

"Call it before the first browser step in an app" gives an explicit trigger point, and "Works for any web app; one outside Cotlet's catalog gets the general method" covers the fallback case. It does not explicitly say when to skip it (e.g., follow-up steps, or when cotlet_apps alone suffices), but the before-the-first-step framing implies subsequent actions use the browser_* tools.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Gymdesk by Cotlet toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources