Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
COTLET_API_KEYYesCotlet.dev API key used to authenticate. Required for tool execution (discovery works without a key) and used by the optional local stdio bridge and Docker environment.

Instructions

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

Zanda through Cotlet.dev. Call zanda_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
zanda_guideA

How to work in Zanda (practice calendars, waitlists, forms, messages and reports): its screens and the sign-in link. Call this first.

zanda_statusA

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

zanda_openA

Open a Zanda page in your signed-in Cloud Browser (default https://my.zandahealth.com) to work with practice calendars, waitlists, forms, messages and reports.

zanda_readA

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

zanda_clickB

Click a numbered element on the current Zanda page.

zanda_typeC

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

zanda_closeA

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

Scored across 7 tools

Disambiguation5/5

Each tool maps to a distinct step in a browser-automation workflow: guide, status check, open, read, click, type, and close. There is no meaningful overlap between reading a page, clicking an element, typing into a field, or opening/closing the session.

Naming Consistency5/5

All tools use the same predictable zanda_ prefix followed by a short lowercase verb or noun. The convention is consistent throughout and each name clearly reflects its action.

Tool Count5/5

Seven tools is well-scoped for a browser-automation wrapper: one orientation tool, one readiness check, and five lifecycle operations for opening, inspecting, interacting with, and closing a session. No tool feels redundant.

Completeness4/5

The surface covers the core lifecycle: check status, open a page, read it, click/type, and close. Minor gaps exist for richer browser interactions such as selecting dropdown options, scrolling, waiting for page loads, or pressing keys, though many of these can be approximated through click and type.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues