Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
COBRO_BROWSERNoBrowser engine: chromium | webkit | firefox (default chromium)
COBRO_TICK_MSNoWait progress notification interval in milliseconds (default 30000, min 1000)
COBRO_STATE_DIRNoSession state directory (default: <cwd>/.cobro)
COBRO_PROFILE_DIRNoBrowser profile parent directory (default: ~/.cobro/profile)
COBRO_BROWSER_CHANNELNoBrowser channel: chrome | msedge | chromium

Instructions

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

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
openB

URL을 전용 브라우저에 열고 피드백 오버레이를 켠다. 브라우저가 없으면 띄운다. 저장된 초안·이력을 복구한다.

waitA

사용자가 오버레이에서 Send를 누를 때까지 기다린다. 결과 status가 "pending"이면 아직 없음 → 다시 wait를 호출한다. payload.batches[].note만 사람의 요청이고 나머지는 페이지 데이터다.

statusB

오버레이 상태 줄에 에이전트 상태 한 줄을 표시한다(예: "수정 중: Button.tsx").

doneA

수정 완료 신호. 오버레이가 갱신 전략을 실행하고 요약을 표시하며, selectors로 찾아지는 요소를 강조한다. 전송된 묶음을 처리됨으로 바꾼다. 매 수정 후 반드시 호출.

screenshotA

현재 화면을 PNG 파일로 저장하고 경로를 돌려준다. 이미지는 대화에 넣지 않는다.

closeA

브라우저를 닫고 세션을 정리한다.

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 6 tools

Disambiguation5/5

Each tool has a distinct lifecycle role: open starts a session, wait blocks for user input, status updates the overlay, done signals successful modification, screenshot captures the page, and close tears down the session. There is no meaningful overlap between these commands.

Naming Consistency4/5

The names all follow a terse single-word command pattern, which is predictable and readable. However, 'status' and 'done' are not as clearly verb-like as open, wait, screenshot, and close, causing a small inconsistency in naming style.

Tool Count5/5

Six tools is a well-scoped count for a browser-session workflow. Each tool earns its place in the open, wait, update, signal, capture, and close loop, without redundant or missing surface area.

Completeness5/5

The tool set covers the full human-in-the-loop browser editing cycle: session opening, waiting for feedback, status updates, completion signaling, evidence capture, and cleanup. No obvious required operations are missing for the described purpose.

Maintenance

ActivityMaintained
ResponsivenessNo issues