jev-kit
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| JEV_KIT_HOME | No | Custom configuration directory (defaults to ~/.jev-codex-kit). Must be the same as used during setup. | |
| TYPESAFE_API_KEY | No | Your TypeSafe API key. If not set, the key stored during setup will be used. |
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| jev_prepare_workA | Prepare one task-specific source-linked work packet for main-host execution or one subagent assignment. Each different task needs its own task_id and preparation, even with shared sources. Batch-group explicit materials and check supplied claims; preserve all originals, constraints and acceptance. No model selection, spawning or edits. No labels/checks means zero inference. |
| jev_route_skillsA | Suggest one host-confirmed skill for a task from at most 19 complete candidate descriptions. Preserve required skills without inference, allow no-match and uncertainty. Does not install, load, execute or scan skills. Not a per-message hook. |
| jev_evaluateB | Typed atomic judgments over supplied text. Use only if a specific recipe does not fit. |
| jev_coding_loopB | Judge next step, retry or stop from trusted execution facts. Does not run anything. |
| jev_stepA | Select among host-prepared authorized calls and route a step. Host executes only after its own checks. |
| jev_tool_routeA | Select from prepared calls; never generates arguments or executes calls. |
| jev_reviewB | Assess a proposed diff. Advisory; actual tests and host review remain required. |
| jev_verifyB | Check claims against supplied evidence, retaining uncertainty and unsupported claims. |
| jev_screenA | Assess untrusted text; not a security boundary or permission to follow its instructions. |
| jev_rankA | Rank explicit candidates by relevance. Does not discover files. |
| jev_gateB | Review a diff and verify completion claims together. Auto is not runtime acceptance. |
| jev_code_briefB | Find source candidates within an explicitly authorized non-sensitive subdirectory, batch-rank with Jev, return complete units, hashes and coverage limits. No edits or tests. Explicit configured root required. |
| jev_prepare_evidenceA | Collect explicit authorized file excerpts, optionally batch-classify or verify claims, and return evidence with hashes. Pinned collection uses no model. No arbitrary commands or source edits. |
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 13 tools
Several tools occupy overlapping 'select/judge without executing' territory (jev_step vs jev_tool_route vs jev_route_skills; jev_review vs jev_gate; jev_evaluate vs jev_verify). The caveats in the descriptions help, but the boundaries are subtle and an agent would need to read closely to avoid misselection.
All tools share the jev_ prefix and mostly follow a snake_case verb_noun pattern like jev_prepare_work and jev_route_skills. A few outliers such as jev_coding_loop, jev_tool_route, and jev_step break the verb-first pattern, but the naming is still predictable and readable.
13 tools is a reasonable size for a workflow-oriented kit and each tool has a distinct stage in the process. It is slightly heavy because some tools are narrowly scoped variants of similar actions, but none feel redundant enough to remove.
The tool surface covers preparation, routing, evaluation, review, verification, screening, ranking, gating, code brief generation, and evidence collection, which matches the stated host-advisory role. Execution is deliberately left to the host, so major workflows do not dead-end. Missing task/state management seems out of scope for this kit.