Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
JEV_BRIDGE_DIRNoPath to the local JevBridge runtime directory. Defaults to %LOCALAPPDATA%\JevBridge\runtime on Windows or ~/.local/share/JevBridge/runtime on Linux/macOS. Required only for tools that invoke the external JevBridge runtime; offline deterministic tools do not require it.

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
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
jev_guardA

Provide advisory risk screening for a shell command using Layer-0 deterministic regex rules and (unless reflex_only=true) System-1 probabilistic evaluation. Does not intercept host execution.

jev_routeB

Provide advisory task complexity and model tier recommendation (requires configured JevBridge runtime).

jev_verifyB

Review caller-supplied task specification, change summary, and test logs for potential evidence gaps (does not run tests or read git diffs directly; requires JevBridge runtime).

jev_rerankA

Rank up to 96 candidate text items against a query in batches of 12 (requires JevBridge runtime).

jev_arbitrateB

Run the offline deterministic 5-factor Meta-Controller to recommend Layer-0 Reflex, System-1 Intuition, System-2 Deep Reasoning, or Human Gate.

jev_benchmarkA

Run the offline deterministic Layer-0 JSONL replay benchmark suite and return accuracy and timing metrics.

jev_autopilotB

Zero-config offline autopilot selector that recommends model tier, reasoning_effort (low/medium/high), and context tier without manual grouping.

jev_chrome_guardC

Zero-popup Chrome M144+ DevToolsActivePort discovery and Layer-0 DLP/SSRF pre-screening for live browser CDP automation.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

B3.3/5.0

Scored across 8 tools

Disambiguation3/5

The tools are mostly distinct, but jev_autopilot, jev_route, and jev_arbitrate all relate to model/reasoning selection and could be confused. Their descriptions differentiate offline vs. runtime and tier vs. reasoning mode, but an agent may still misselect among them.

Naming Consistency4/5

All tool names use a consistent jev_ snake_case prefix, making them easy to recognize as a set. However, some names are verbs (verify, rerank, route) while others are nouns or compound nouns (autopilot, chrome_guard, benchmark), so the verb_noun pattern is not strict.

Tool Count5/5

Eight tools is a well-scoped count for this cognitive/advisory toolkit. Each tool has a distinct high-level function, and there is no obvious filler or redundancy.

Completeness4/5

The surface covers benchmarking, routing, arbitration, guarding, verification, and reranking, which appears complete for the stated advisory domain. Minor gaps exist around runtime status/configuration checks and explicit cognitive state management, but agents can likely work around them.

Maintenance

ActivityNo data
ResponsivenessOutdated data