Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
COTLET_API_KEYYesAPI key from the Cotlet.dev console. Required by the optional local adapter and used as an Authorization: Bearer header for Codex and Claude Code.

Instructions

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

eZee Optimus through Cotlet.dev. Call ezee_optimus_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
ezee_optimus_guideA

How to work in eZee Optimus (restaurant orders, kitchen tickets and bills): its screens and the sign-in link. Call this first.

ezee_optimus_statusA

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

ezee_optimus_openA

Open a eZee Optimus page in your signed-in Cloud Browser (default https://app.ipos247.com) to work with restaurant orders, kitchen tickets and bills.

ezee_optimus_readA

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

ezee_optimus_clickB

Click a numbered element on the current eZee Optimus page.

ezee_optimus_typeC

Type text into a numbered field on the current eZee Optimus page.

ezee_optimus_closeA

Close the eZee Optimus 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

Disambiguation4/5

Each tool has a distinct browser-automation role: status, guide, open, read, click, type, and close. The only mild overlap is between status/guide as pre-work tools and open/read as page-access tools, but descriptions make their boundaries clear.

Naming Consistency4/5

All tools use the same ezee_optimus_ prefix and snake_case convention, making the set predictable. Most names are verb-based except status and guide, which are minor deviations but still readable and consistent with the prefix.

Tool Count5/5

Seven tools is well-scoped for a browser-automation workflow covering readiness, guidance, session lifecycle, and page interaction. No tool feels redundant or extraneous.

Completeness4/5

The set covers the core lifecycle: check status, read guide, open page, inspect page, click, type, and close. Minor gaps exist for common browser actions like waiting, scrolling, selecting options, or navigating back, but agents can likely work around them.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues