openjev-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| OPENJEV_MODEL | No | Model alias sent when a call does not name one. Unset uses the service default, openjev. | |
| OPENJEV_API_KEY | Yes | Required. Bearer token for the API. | |
| OPENJEV_BASE_URL | No | API origin, for a proxy or a test double. Default: https://api.openjev.sh | https://api.openjev.sh |
| OPENJEV_TIMEOUT_MS | No | Per-attempt timeout, 1000–600000. Default: 30000 | 30000 |
| OPENJEV_MAX_RETRIES | No | Retries after the first attempt, 0–10. Default: 2 | 2 |
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_askA | Send one shared context and one or more independent questions to Jev (TypeSafe System One) and get typed judgments back — not prose. How to design the call:
Reading the result: answers come back under |
| jev_choiceA | Ask one question whose answer is exactly one of a set of options you define. Use for a category, a route, or a selection from a closed list — not for a degree and not for a yes/no. Write the judgment in Returns the selected option, the full probability distribution, and |
| jev_scoreA | Ask one question whose answer is a position on an ordered scale you define. Use for degree, severity, or intensity. Returns the score, the |
| jev_noulA | Ask one yes/no question and get its probability. Use when the condition either holds or does not, and the probability is more useful than a category. Name the condition precisely in Returns a value between 0 and 1: near 1 yes, near 0 no, near 0.5 uncertain. It measures probability, not intensity, and there is no separate confidence field — a confident no is near 0, not near 0.5, so read low values as evidence against rather than as low confidence. |
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 4 tools
Each single-question tool has a clearly distinct response type (choice, score, noul), and jev_ask is explicitly the batch variant. There is minor overlap because jev_ask can also ask choice, score, or noul questions, but the batch-vs-single distinction is clear.
All tools share the consistent 'jev_' prefix, making them instantly recognizable. The suffix mixes a verb ('ask') with response-type nouns ('choice', 'score', 'noul'), but the pattern is still predictable and readable.
Four tools is a well-scoped set for a specialized question-answering server: one batch entry point and three focused question types. Each tool earns its place without redundancy or bloat.
The tool surface covers the core domain of typed judgments well: batch asking plus choice, score, and yes/no variants. Minor gaps such as conversation history or model configuration exist, but they are not essential to the stated purpose.