jev-engineering
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| JEV_GATE_LOG | No | Path to decisions log. | ~/.jev-gate/decisions.jsonl |
| JEV_GATE_MODE | No | Mode of operation: observe, guard or enforce. | observe |
| JEV_DENY_ABOVE | No | Destructive probability that denies outright. | 0.90 |
| JEV_ALLOW_BELOW | No | Destructive probability that allows outright. | 0.10 |
| JEV_GATE_TIMEOUT | No | Seconds before failing open. | 5 |
| TYPESAFE_API_KEY | No | Alternative API key for TypeSafe's Jev, can be used instead of OPENROUTER_API_KEY. | |
| OPENROUTER_API_KEY | No | Your OpenRouter API key. TYPESAFE_API_KEY also works. | |
| JEV_CONFIDENCE_FLOOR | No | Below this confidence, escalate to a human. | 0.45 |
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
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| check_actionA | Judge whether an action is safe to take, before taking it. Returns allow, ask or deny with a probability, a confidence and a reason. Call this before anything destructive, irreversible, or outside what the user asked for. action: the exact thing about to happen, such as a shell command, an email body, or a description of the API call. user_asked_for: what the human actually requested, verbatim. Send it. A judgement about authorization is worthless without it. pack: which question set to use. One of: {packs}. |
| route_turnA | Pick which model tier should handle this turn, before spending on it. Returns a tier, the odds on each, and a confidence. Call it at the start of a turn so a rename does not cost what an architecture decision costs. task: what this turn is being asked to do. tiers: your tier names, cheapest first. Defaults to fast, standard, frontier. |
| keep_contextA | Decide which pieces of context still earn their place, in one call. Nothing is rewritten or summarised. Each item is kept verbatim or dropped, because a summary silently loses the exact path or error you needed later. items: the context pieces, usually tool calls and their results. goal: what the agent is trying to finish. budget: the share to keep when scores are close. 0.5 keeps half. |
| rank_optionsA | Rank a list of options against one criterion, in a single call. Cheaper and faster than asking a chat model to sort them, and it returns a probability per option rather than an opinion. Good for choosing a file, a tool, a model tier, or reordering search results. options: up to 255 choices. criterion: what makes one option better, as a plain statement. context: whatever the options should be judged against. |
| gate_statsA | What the gate has decided so far: counts, verdict split and spend. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Each tool addresses a distinct decision or operation: safety checks, model tier routing, context pruning, option ranking, and statistics. Even though they share a 'gate' theme, the descriptions clearly separate their purposes, leaving no ambiguity.
Four tools follow a clear verb_noun pattern (check_action, route_turn, keep_context, rank_options), while gate_stats is a noun_noun compound. This is a minor deviation but still consistent in style (lower_snake_case) and readable.
Five tools is well-scoped for a gating/decision server, covering the essential operations without redundancy or bloat. It feels complete for the stated domain.
The tools cover the full decision lifecycle: pre-action safety checks, turn routing, context management, option ranking, and post-hoc statistics. A configuration or reset tool might be missing, but the core surface is solid and no critical gaps are evident.