Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
COTLET_API_KEYYesYour Cotlet.dev API key, used as a Bearer token for the hosted MCP server and for the local stdio adapter. 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.

GoReminders through Cotlet.dev. Call goreminders_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
goreminders_guideA

How to work in GoReminders (review appointments, customer replies and reminder workflows): its screens and the sign-in link. Call this first.

goreminders_statusB

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

goreminders_openA

Open a GoReminders page in your signed-in Cloud Browser (default https://www.goreminders.com) to work with review appointments, customer replies and reminder workflows.

goreminders_readB

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

goreminders_clickB

Click a numbered element on the current GoReminders page.

goreminders_typeB

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

goreminders_closeA

Close the GoReminders 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

Disambiguation4/5

Each tool has a clear role: guide/status for setup, open/read/click/type/close for browser interaction. There is slight overlap between open and status in readiness context, but the descriptions distinguish them well. An agent can reliably choose the right action.

Naming Consistency5/5

All tools use the same goreminders_ prefix followed by a concise snake_case verb or noun. The pattern is consistent and predictable. No mixed casing or conflicting naming styles.

Tool Count5/5

Seven tools are well scoped for a guided browser automation server. Each tool maps to a distinct step in the workflow: onboarding, session management, and page interaction. There are no redundant tools.

Completeness4/5

The surface covers the core browser lifecycle: open, read, click, type, and close, plus guide and status. Minor gaps exist for navigation actions like scrolling or pressing Enter, but most workflows can be handled through clicking and typing. Overall the tool set is complete for the stated GoReminders use case.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues