Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
COTLET_API_KEYYesYour Cotlet API key, obtained at https://cotlet.dev/app. Used as a Bearer token (Authorization: Bearer $COTLET_API_KEY) or passed via the env block when running the server locally. Without it, tool calls fail 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.

Provision through Cotlet.dev. Call provision_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
provision_guideA

How to work in Provision (pre-construction bid documents, scope gaps, scope packages, contract risks and review checklists): its screens and the sign-in link. Call this first.

provision_statusA

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

provision_openB

Open a Provision page in your signed-in Cloud Browser (default https://provision.com) to work with pre-construction bid documents, scope gaps, scope packages, contract risks and review checklists.

provision_readA

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

provision_clickB

Click a numbered element on the current Provision page.

provision_typeB

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

provision_closeA

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

Scored across 7 tools

Disambiguation5/5

Each tool has a clearly distinct role: onboarding guidance, account readiness, opening a browser session, reading the page, clicking, typing, and closing the session. The read/click/type tools operate on numbered page elements and are easily separable. There is no meaningful overlap between tools.

Naming Consistency5/5

All tools use a consistent provision_ prefix followed by a concise verb or noun (guide, status, open, read, click, type, close). The naming is predictable, readable, and uniform in snake_case style.

Tool Count5/5

Seven tools is well-scoped for a browser-based workflow assistant covering guidance, readiness, session lifecycle, and basic page interaction. Each tool earns its place without redundant operations.

Completeness4/5

The surface covers the essential lifecycle: learn, check readiness, open, read, interact, and close. Minor gaps exist around richer browser operations such as scrolling, waiting, or explicit navigation controls, but the core workflow is well covered.