Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
JEV_MODELNoModel override for the provider
CMD_API_KEYNoAPI key for Command Code provider
VERCEL_API_KEYNoAlternative API key for Vercel AI Gateway provider
OPENCODE_API_KEYNoAPI key for OpenCode Zen provider
TYPESAFE_API_KEYNoAPI key for TypeSafe AI provider
AI_GATEWAY_API_KEYNoAPI key for Vercel AI Gateway provider
OPENROUTER_API_KEYNoAPI key for OpenRouter provider (alpha access)
COMMAND_CODE_API_KEYNoAlternative API key for Command Code provider
VERCEL_AI_GATEWAY_API_KEYNoAnother alternative API key for Vercel AI Gateway provider

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
}

Tools

Functions exposed to the LLM to take actions

NameDescription
jev_triage_test_failureA

Triages test failure traceback, compilation error, or runtime exception using Jev System One non-autoregressive decision classification (70-300ms, zero LLM generation). Detects missing environment packages, flaky transient glitches, or deep logic defects.

Use when: An agent encounters a test failure, traceback, compiler error (e.g. TS2307, ModuleNotFoundError, E0463), or needs to decide whether to invoke a frontier LLM. Do NOT use when: Tests pass, or for general code review or feature generation.

Returns: JSON object with 'category' (env_missing, flaky_transient, deep_logic, no_failure), 'skip_llm' (boolean: true if resolvable deterministically without frontier LLM), and 'action_recommendation' (string with concrete recovery action).

jev_check_abortA

Guards against doom loops, repetitive circular retries, dead-ends, and destructive refactoring before burning frontier reasoning tokens. Evaluates the agent's proposed plan against recent attempt history.

Use when: An agent is about to retry a failed step, execute a code edit after previous failed attempts, or before embarking on a potentially circular fix. Do NOT use when: Making the first attempt on a fresh task with no prior failure history.

Returns: JSON object with 'should_abort' (boolean: true if the trajectory is stuck in a circular loop), 'abort_probability' (number: 0.0 to 1.0), 'action' (string: PROCEED, HALT, PIVOT), and 'reasoning_summary' (string explaining the decision).

jev_route_taskA

Routes a programming task to the minimal sufficient model tier (deterministic script, lightweight flash model, or heavy frontier reasoning model) to minimize latency and token expenditure.

Use when: Starting a new task, refactoring step, or bug fix to choose between lightweight models and expensive reasoning frontier models. Do NOT use when: Diagnosing test execution tracebacks (use jev_triage_test_failure instead).

Returns: JSON object with 'selected_tier' (string: deterministic, lightweight, heavy), 'complexity_score' (number: 1.0 to 5.0), 'recommended_model' (string), and 'rationale' (string).

jev_verify_completionA

Calibrates step completion against acceptance criteria using typed rubric scoring. Evaluates whether produced evidence proves the task is finished without running redundant review loops.

Use when: An agent believes a task or milestone is complete and wants to verify acceptance criteria before concluding. Do NOT use when: Work is still underway or tests are actively failing.

Returns: JSON object with 'is_verified' (boolean: true if acceptance criteria are satisfied with proof), 'satisfaction_probability' (number: 0.0 to 1.0), 'rigor_score' (number: 1.0 to 4.0), 'needs_rework' (boolean), and 'confidence' (number: 0.0 to 1.0).

jev_modulate_reasoning_effortA

Dynamically modulates reasoning effort (low, medium, high, etc.) and generation stability lease steps for the immediate LLM call. Maps provider-specific parameters for OpenAI (GPT-6 Astra/o3), DeepSeek (V4.1-Flash/R1), Qwen (3.8 Max), Anthropic (Claude Fable 5.1), and Gemini (3.8 Thinking) to prevent reasoning token waste.

Use when: Preparing a prompt or tool call for a reasoning-capable LLM to calibrate thinking effort according to task complexity. Do NOT use when: Calling standard non-reasoning models or local deterministic scripts.

Returns: JSON object with 'effort' (string), 'provider' (string), 'provider_params' (object with provider-native kwargs), 'is_reasoning_supported' (boolean), 'cache_safe_recommendation' (string), and 'lease_steps' (integer).

jev_evaluate_nudgeA

Evaluates whether an autonomous agent paused prematurely with unfinished work or unverified changes (covering workflow phases: research, ask, plan, execute, verify, complete). Vetoes nudges when waiting on user input or when repeated nudges make no progress.

Use when: A background worker or agent loop stops and you need to determine if it should be nudged to continue autonomously. Do NOT use when: The agent explicitly requested user confirmation or required credentials.

Returns: JSON object with 'should_nudge' (boolean), 'workflow_phase' (string: research, ask, plan, execute, verify, complete), 'action' (string: NUDGE, WAIT, STOP), and 'confidence' (number: 0.0 to 1.0).

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 6 tools

Disambiguation5/5

Each tool targets a distinct decision point in the agent workflow: triage failure, check abort, route task, verify completion, modulate reasoning, and evaluate nudge. The only potential overlap between route_task and modulate_reasoning_effort is well-clarified by descriptions that distinguish tier selection from per-call reasoning parameter mapping.

Naming Consistency5/5

All tool names follow a consistent jev_ prefix with snake_case verb_noun or verb_noun_noun structure (e.g., jev_triage_test_failure, jev_route_task). No deviations in style or convention.

Tool Count5/5

Six tools is well-scoped for an agent harness, with each tool addressing a unique decision point without redundancy. The set is neither too thin nor too heavy for the purpose.

Completeness4/5

The tools cover the core agent lifecycle decisions: model routing, reasoning effort, failure triage, abort detection, completion verification, and nudge evaluation. A minor gap exists in explicit state or attempt history management, but agents can work around this externally.

Maintenance

ActivityMaintained
ResponsivenessNo issues