Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
COTLET_API_KEYYesAPI key from Cotlet.dev (https://cotlet.dev/app). Required for tool calls; 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.

MioCommerce through Cotlet.dev. Call miocommerce_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
miocommerce_guideA

How to work in MioCommerce (customers, bookings, quotes, invoices and service provider schedules): its screens and the sign-in link. Call this first.

miocommerce_statusB

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

miocommerce_openA

Open a MioCommerce page in your signed-in Cloud Browser (default https://signin.miocommerce.com) to work with customers, bookings, quotes, invoices and service provider schedules.

miocommerce_readA

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

miocommerce_clickB

Click a numbered element on the current MioCommerce page.

miocommerce_typeC

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

miocommerce_closeA

Close the MioCommerce 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 role: status checks readiness, guide explains the workflow, open/read/click/type/close are standard browser primitives. The only mild overlap is status vs guide, both being 'orientation' tools with 'call this first' style guidance, but their descriptions distinguish them adequately.

Naming Consistency5/5

Every tool uses the same miocommerce_ prefix followed by a single, action-oriented verb (status, guide, open, read, click, type, close). The pattern is uniform and immediately readable.

Tool Count5/5

Seven tools is well-scoped for a browser-bridge server: two setup/orientation tools plus five minimal interaction primitives. No tool feels redundant or extraneous.

Completeness3/5

The surface covers open/read/click/type/close but lacks common browser operations: scrolling on long pages, navigating to a specific URL or going back, and selecting from dropdowns. These gaps will likely cause dead ends on real booking/invoice workflows that require scrolling or form selection.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues