Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
COTLET_API_KEYYesYour Cotlet.dev API key. Get one at https://cotlet.dev/app. Required for authenticated tool calls; without it, tool calls return a message asking you to set COTLET_API_KEY.

Instructions

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

Zenoti through Cotlet.dev. Call zenoti_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
zenoti_guideA

How to work in Zenoti (read appointments, draft guest replies and review front desk reports): its screens and the sign-in link. Call this first.

zenoti_statusA

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

zenoti_openB

Open a Zenoti page in your signed-in Cloud Browser (default https://www.zenoti.com) to work with read appointments, draft guest replies and review front desk reports.

zenoti_readB

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

zenoti_clickB

Click a numbered element on the current Zenoti page.

zenoti_typeC

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

zenoti_closeA

Close the Zenoti 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.6/5.0

Scored across 7 tools

Disambiguation5/5

Each tool maps to a distinct browser-session operation: setup guidance, account readiness, opening a page, reading the page, clicking, typing, and closing. The only mild overlap is that both zenoti_guide and zenoti_status are pre-work steps, but their purposes are clearly different.

Naming Consistency4/5

All tools use a consistent zenoti_ prefix and snake_case style, making the set easy to scan. There is a minor deviation because guide and status are nouns while the remaining tools are verbs, but the pattern remains predictable.

Tool Count5/5

Seven tools is a well-scoped set for browser-based interaction with Zenoti. Each tool has a clear role in the session lifecycle and none feels redundant.

Completeness4/5

The surface covers the core browser automation lifecycle: open, inspect, interact, and close. Minor gaps such as explicit navigation/back or keyboard submission are not present, but click and type likely let agents work around them.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues