Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
COTLET_API_KEYYesCotlet.dev API key, created in the Cotlet console for editors or scripts. Used as "Authorization: Bearer $COTLET_API_KEY". Without it, a tool call answers: "Set COTLET_API_KEY. Get a key at https://cotlet.dev/app".

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

Fitune through Cotlet.dev. Call fitune_guide first. Set COTLET_API_KEY (https://cotlet.dev/app).

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}

Tools

Functions exposed to the LLM to take actions

NameDescription
fitune_guideA

How to work in Fitune (studio classes, bookings, memberships, invoices and payroll): its screens and the sign-in link. Call this first.

fitune_statusB

Check that your Cotlet.dev account and Fitune are ready: account, credits and Fitune connection.

fitune_openA

Open a Fitune page in your signed-in Cloud Browser (default https://admin.fitune.io) to work with studio classes, bookings, memberships, invoices and payroll.

fitune_readB

Read the current Fitune page: its text and numbered buttons, links and fields.

fitune_clickB

Click a numbered element on the current Fitune page.

fitune_typeB

Type text into a numbered field on the current Fitune page.

fitune_closeA

Close the Fitune browser session when the work is done, so credits stop running.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.5/5.0

Scored across 7 tools

Disambiguation4/5

Each tool maps to a distinct step in a browser automation lifecycle (guide, status, open, read, click, type, close), so selection is largely unambiguous. The only mild overlap is between fitune_guide and fitune_status, both framed as pre-flight checks, with competing 'call this first' guidance.

Naming Consistency4/5

All seven tools share a uniform snake_case 'fitune_' prefix and short, readable names. Minor deviation: open/read/click/type/close are verbs while guide and status are nouns, so the pattern isn't a strict verb_noun convention.

Tool Count5/5

Seven tools is well-scoped for driving a single web app: one setup, one session open/close pair, one read, and two interaction primitives. Nothing appears redundant or padded.

Completeness3/5

The core loop (open → read → click/type → close) is covered, but there is no scroll, no key/submit primitive, and no select/dropdown handling, which will bite on long or form-heavy studio admin pages. Agents can partially work around this by re-reading or re-opening with an explicit URL.