Skip to main content
Glama

Eversports Studio Manager 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 Eversports Studio Manager it covers these actions: Browse and filter customers, View a customer profile, Invite customers to activate their account, Export all or filtered customers (CSV), Export customers to Mailchimp, Create classes and trainings, Create courses, workshops, retreats, events, camps and educations, Bulk extend activities, Cancel a single appointment, with optional email notification, Bulk cancel appointments, with optional email notification, Cancel a course, workshop or event, Add notes to class sessions, Use activity templates, Create, edit and cancel private sessions (BETA), Request or accept a teacher substitution, View the Sign-in participant list, Sign a customer in to an activity, Create a recurring sign-in, Sign a customer out (regular cancellation), Sign a customer out as a late cancellation, Sell a product from the Sign-in, Settle bookings without a product, View products and product analysis, Create a block card or time card, Terminate a membership, with optional confirmation email, Create an article, Sell a product (Financials > Selling), View and filter invoices, Print or email a single invoice, Pay or mark open invoices as paid, Cancel an invoice (refunds online payments automatically), Create a credit note (negative invoice), Download activity reports (Analytics > Reports), Create a discount code (Marketing > Promotions), Give an employee or trainer login rights and assign a role, Set up automated teacher payroll (Smart Payroll extension), Edit master data, invoice settings and financial settings, Allow aggregator bookings on an activity, Limit bookings or block customers, Configure spot selection (spot booking extension), Create a referral code (Your Bonus), Contact Eversports support via in-app chat, Edit appointments, Configure booking questions, Archive restore customer, Edit sold entitlement, Assign existing service, Assign membership, Update membership prices, Pause membership, List export active memberships, Configure legal documents, Configure self check in, Configure email journeys, Configure customer referrals, Export customer referrals, View voucher journal, Create video bundle, Create sepa mandate, Request additional customer fields.

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: Eversports Studio Manager.
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 readOnly/idempotent/non-destructive, so the safety profile is covered; the description adds genuinely new context by stating it is 'Free, no browser session', meaning the agent can call it without consuming a browser slot or credits. It also discloses what comes back (browser choice, sign-in link, method, screens, menus, notes, dedicated tools). It doesn't describe response shape or how the task parameter shapes the answer.

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 two sentences are well front-loaded, but the final 60-plus-item comma-separated inventory of Eversports Studio Manager actions is a single run-on block that is hard to scan and largely unusable as guidance. It inflates the description massively for a list that duplicates what the per-action sibling tools already imply.

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 lookup with no output schema, the description covers when to call, scope of app coverage, cost, and the kinds of content returned. The only real shortfall is that it never says how the returned guidance relates to the dedicated eversports_studio_manager_* tools it names.

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 the schema, including the default app. The description adds nothing parameter-specific beyond listing example app actions, so the baseline 3 applies.

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 description makes clear this is a guide/knowledge lookup that returns workspace-specific browser choice, sign-in link, and step-by-step method before any clicking happens, which separates it from the cotlet_browser_* action tools. The opening phrase 'How to work in an app' restates the title rather than naming a crisp verb like 'get', but the surrounding detail pins down the resource and the return content.

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 explicit sequencing relative to the browser tools, and 'Works for any web app; one outside Cotlet's catalog gets the general method' sets the coverage boundary. It does not state when NOT to call it (e.g., mid-task re-reads), but an agent has enough to decide correctly.

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