jev-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| OPENCODE_API_KEY | No | Optional OpenCode Zen key, only needed if using endpoint='zen'. | |
| TYPESAFE_API_KEY | Yes | TypeSafe API key required to use Jev models. |
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
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| jev_evaluateA | Evaluate state against typed questions. Returns {model, answers, usage}. questions: {"id": {"type": "noul"|"choice"|"score", "instructions": ..., "criteria": {...} or [...]}}. Batch independent questions in one call; they run in parallel. endpoint: "direct" (TYPESAFE_API_KEY) or "zen". |
| jev_noulC | Yes/no judgment. Returns {type, noul (0=no..1=yes)}. Near 0.5 = uncertain. |
| jev_choiceB | Pick one option. criteria: {"option": "rubric..."}. Returns choice + probabilities + confidence. |
| jev_scoreC | Rate along ordered levels (2-10 concrete descriptions). Returns score + legend + probabilities. |
| jev_modelsA | List models your key can use (GET /v1/models on direct; static list on zen). |
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
jev_evaluate subsumes the other evaluation tools, creating potential overlap. The descriptions clarify that evaluate is for batched/mixed types while the specialized tools handle single questions, but an agent could still be unsure which to use for a one-off noul or choice query.
All tools share the 'jev_' prefix in lowercase snake_case, making them easily recognizable as a family. The names mix verbs and nouns (evaluate, models vs noul, choice, score), but the uniform prefix and short, predictable tokens keep the pattern strong.
Five tools is a well-scoped size for an evaluation API wrapper. It includes a general evaluator, three specialized question types, and a model discovery utility without unnecessary bloat.
The toolset covers all declared question types (noul, choice, score) and provides the necessary model listing capability. It lacks history or configuration management, but those are not implied by the server's focused purpose.