openrouter-jev-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| JEV_LOG_DIR | No | Directory where diagnostic logs are written. Defaults to ~/.local/state/jev-gateway. | ~/.local/state/jev-gateway |
| OPENROUTER_API_KEY | Yes | Your OpenRouter API key used to access the Jev model through OpenRouter's Decisions endpoint. |
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 |
|---|---|
| jev_checkC | Evaluate a Noul proposition against string, object, or list state. |
| jev_classifyC | Choose one caller-defined label for string, object, or list state. |
| jev_scoreC | Score string, object, or list state against ordered caller-defined levels. |
| jev_evaluateC | Evaluate a named map of Noul, Choice, and Score questions. |
| jev_healthA | Report OpenRouter configuration readiness; connectivity is unverified unless explicitly probed. |
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 has a distinct evaluation purpose: single check, classification, scoring, batch evaluation, and health reporting. The only mild overlap is between jev_check and jev_evaluate, since evaluate can contain Noul questions, but the singular versus map distinction keeps them separable.
All tools share the jev_ prefix and use lowercase snake_case, creating a clear family resemblance. The main inconsistency is that four tools are verb-based (check, classify, score, evaluate) while jev_health is a noun, but the pattern remains predictable.
Five tools is a well-scoped set for an evaluation-oriented server: single operations plus a batch operation plus health. Each tool has a distinct role without unnecessary redundancy.
The tool surface covers the core evaluation lifecycle: primitive checks, categorical classification, ordered scoring, batched evaluation of mixed question types, and health/configuration readiness. No significant dead ends or missing core operations are apparent for the stated domain.