Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
COTLET_API_KEYYesYour Cotlet.dev API key, obtained at https://cotlet.dev/app. Required for NetGrind tool calls; without it, tool calls answer: "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.

NetGrind through Cotlet.dev. Call netgrind_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
netgrind_guideA

How to work in NetGrind (review submissions, track Players and manage Shop rewards): its screens and the sign-in link. Call this first.

netgrind_statusA

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

netgrind_openA

Open a NetGrind page in your signed-in Cloud Browser (default https://play.netgrind.online) to work with review submissions, track Players and manage Shop rewards.

netgrind_readA

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

netgrind_clickB

Click a numbered element on the current NetGrind page.

netgrind_typeB

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

netgrind_closeA

Close the NetGrind 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 clearly distinct step in a browser workflow: onboarding (guide), readiness check (status), session lifecycle (open/close), and page interaction (read/click/type). There is no meaningful overlap — read only inspects, click/type only act on numbered elements, and guide/status are explicitly differentiated by their wording.

Naming Consistency4/5

All seven tools share a uniform netgrind_ snake_case prefix, which makes the set highly predictable. The only minor deviation is that guide and status are nouns while open/read/click/type/close are verbs, though this is idiomatic and not confusing.

Tool Count5/5

Seven tools is well-scoped for a single-site browser automation server: one discovery step, one session-setup step, three interaction primitives, one lifecycle teardown, and one status check. Every tool earns its place with no filler.

Completeness4/5

The core loop — open a page, read its elements, click and type, then close — plus onboarding and readiness checks covers the stated review/Player/Shop workflows. Minor gaps exist for navigation (back/forward), scrolling on long pages, and explicit submit/select actions, which agents must work around via numbered buttons and links.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues