JEVULON VII (JVII)
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| sentinel_shield_inspectA | Pre-flight safety inspection for HIGH-RISK, destructive, or irreversible system operations ONLY (e.g. broad deletions, system path wipes, dropping databases, running untrusted remote scripts, or network exfiltration). DO NOT call this tool for routine coding: file reads, code edits, git status/diff/log/branch, package installs (npm/bun/pip), or build/test runs — routine development does not require inspection. |
| sentinel_approve_escalationA | Operator authorization for one escalated action. Approvals are single-use, bound to the exact action payload, and expire. Approvals must be attributed: pass approvedBy with your host's operator identity — unattributed approvals, and decisions attributed to the identity that requested the escalation, are both refused. Configure your MCP host to always require human confirmation for this tool — the server cannot verify who calls it. |
| sentinel_oversight_monitorC | Evaluates a worker trace for retry loops, deadlocks, and toxic failure patterns (continue / quarantine / reroute / halt). |
| sentinel_superviseB | Stigmergic task dispatcher backed by the recovery supervisor: |
| sentinel_get_statusA | Returns supervisor state, blackboard counts, pending escalations, and local usage counters. |
| sentinel_presenceA | Shared presence board for every agent working in this repository (advisory — it never blocks an action). Quick usage: • Claim files before writing: { action: 'claim', paths: ['src/file.js'], mode: 'edit', note: 'why' }. • Release files when done: { action: 'release', paths: ['src/file.js'] }. • Checkpoint changes: { action: 'checkpoint' }. • Read active board: { action: 'read' }. |
| sentinel_code_reviewA | JEVULON VII Pro code review (Anti-Slop Sieve): audits one file or snippet under the neutral-state 3-run protocol and returns the modal smell label, complexity (cx) & security hazard (hz) scores, gate verdicts, and the refactor directive. Call it before marking a task complete and fix the flagged slop first; a fired abort gate means completion is blocked. Requires a Pro/Team license token in JVII_TOKEN; the code under review goes only to your own BYOK JEV endpoint (never scraped). |
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 7 tools
Each tool has a distinct primary role: dispatcher (supervise), safety inspection (shield_inspect), authorization (approve_escalation), trace evaluation (oversight_monitor), status read, code review, and presence/coordination. There is some conceptual overlap in the safety cluster — supervise's halt/fail, oversight_monitor's halt verdict, shield_inspect, and approve_escalation all touch escalation/failure handling — but the descriptions make the boundaries readable.
All seven tools share a consistent `sentinel_` prefix and snake_case formatting, which is strong. The suffixes are slightly loose in form (verb like `supervise`, noun_verb like `shield_inspect`, plain noun like `presence`), but the overall convention is predictable.
Seven tools is well-scoped for a multi-agent supervision/coordination server and sits comfortably in the ideal 3-15 range. Each tool earns its place with an identifiable function, and there is no bloat.
The surface covers the coordination lifecycle: plan/dispatch (supervise), pre-flight safety (shield_inspect), approval (approve_escalation), monitoring (oversight_monitor), status (get_status), quality gate (code_review), and presence (presence). Coverage is broad with only minor potential gaps, and no obvious dead ends for the stated supervision purpose.