Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
TYPESAFE_API_KEYNoDirect TypeSafe API key, alternative to OPENROUTER_API_KEY.
OPENROUTER_API_KEYNoAPI key for Jev Decisions via OpenRouter (recommended).
TEXT_MODEL_API_KEYNoAPI key for search/filter text entry; the default example uses OpenRouter.

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": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
jev_browseA

Start a new browser session and advance a read-only browsing goal.

Use this for finding, filtering, or opening products on a public website. It executes at most max_steps (1–30) before returning a session_id, visible page evidence, and recent actions. Do not use it for login, checkout, payment, uploads, or any task that enters personal or financial data.

jev_statusA

Inspect a live Jev browser session without taking another browser action.

Use it after jev_browse to reason from the current URL, visible text, supported controls, and recent actions. It does not load a page, click a control, scroll, or generate model requests.

jev_stopA

Close one Jev-owned Chrome target and remove its session.

Call this when product research is complete or after an unrecoverable block. The session_id becomes invalid immediately; this never affects tabs outside the Jev-owned browser target.

jev_extract_productsA

Extract product name, price, rating, details, and link from currently visible product cards.

Use this after jev_browse reaches a results or product page. This is best-effort read-only DOM extraction; it does not scroll, click, or infer fields that are not visible, so verify important price or stock data.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4.4/5.0

Scored across 4 tools

Disambiguation5/5

Each tool has a clearly distinct role: browse starts/advances sessions, status inspects without acting, extract parses visible product cards, and stop closes the session. There is no functional overlap or ambiguity between them.

Naming Consistency4/5

All tools share the 'jev_' prefix and are short, readable command-style names. 'jev_status' is a noun rather than a verb like the others, but this is a minor deviation that does not harm predictability.

Tool Count5/5

Four tools are well-scoped for a read-only browser automation server focused on product research. Each tool serves a distinct stage in the session lifecycle with no redundancy.

Completeness5/5

The tool set covers the full workflow: start/advance browsing, inspect session state, extract product data, and close the session. There are no obvious dead ends or missing lifecycle operations for the stated purpose.

Maintenance

ActivityMaintained
ResponsivenessNo issues