Skip to main content
Glama
Sign In

Eversports Studio Manager by Cotlet

by dev.cotlet
OverviewDiscussionsAdmin

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 Eversports Studio Manager it serves 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_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?

The annotations already mark the tool read-only, non-destructive, open-world, and non-idempotent, so the remaining burden is light. The description adds the main context an agent would otherwise miss: it targets the user's signed-in real browser, it reuses the site's existing tab before opening a new one so the user's tabs are preserved, and it returns the visible page content. It does not say how long startup takes or what happens if the URL fails to load.

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 useful part is two front-loaded sentences at the start. After that come roughly seventy enumerated Eversports Studio Manager actions ('Invite customers to activate their account, Export customers to Mailchimp, Create classes and trainings...'), which read as keyword filler and carry no instructions the agent can act on. The length dilutes the signal that matters.

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-start tool, the description covers starting the browser, tab placement, and what comes back. Combined with the fully documented schema, an agent has what it needs. The only shortfall is the missing failure or timeout behavior and the noise of the action list.

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%, and the schema already explains the non-obvious `app` parameter (leave it out unless cotlet_app_guide names an app's own Cloud Browser) and the URL format. The description adds only the open-tab-versus-new-tab routing behavior, which is a modest gain over the schema. A baseline 3 fits, because the schema already 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?

The first sentence gives a specific verb and resource: starts the user's Cloud Browser (a real signed-in Chrome on Cotlet) and opens a URL. It also says 'Call it first' and describes what the tool returns (elements and text in view), which separates it from read, navigate, and screenshot. What it lacks is an explicit contrast with cotlet_browser_navigate, which sounds close in purpose.

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' is an explicit ordering instruction, and the note that the response is the page afterward tells the agent when to stop and inspect. It does not, however, say when to use navigate, tabs, or read instead, or name any alternative sibling, so the routing guidance is incomplete.

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

All Eversports Studio Manager 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