Jev Decision MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| JEV_TIMEOUT_MS | No | Total request deadline including retries, in milliseconds (1-120000). | 30000 |
| TYPESAFE_API_KEY | Yes | TypeSafe API key required for live Jev decisions. | |
| TYPESAFE_DEFAULT_MODEL | No | Default TypeSafe Jev model. | jev-latest |
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_decideA | Evaluate supplied context using TypeSafe Jev. Batch independent, narrow questions in one call: choice selects a provided label; score returns a position on 2–10 ordered levels (0-based); noul returns probability of yes, not intensity. Supply relevant evidence and full instructions; question IDs are not sent to the model. Include an other/none choice when appropriate. Questions cannot use each other's answers. Returns raw judgments, probabilities, confidence for choice/score, and token usage. Use caller-defined policies for uncertainty. This sends the supplied state and questions to TypeSafe and may incur API charges. It does not execute selected actions. |
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 1 tool
With only one tool, there is no possibility of confusion between tools. The tool's internal modes (choice, score, noul) are clearly delineated within the description, so an agent can unambiguously select this tool for any decision-related task.
The single tool name 'jev_decide' follows a clear prefix-verb pattern (server name + action). Since there is only one tool, there is no inconsistency to evaluate; the naming is predictable and matches the server's purpose.
One tool is slightly thin by general guidelines, but this server is highly specialized for decision-making. The tool consolidates multiple decision types into a single callable interface, making a larger tool count unnecessary. The count is reasonable for the narrow scope.
The tool comprehensively covers the decision-making domain: choice selection, scoring on ordered levels, and probability of a yes outcome. It also provides confidence metrics, token usage, and handles batching of independent questions. There are no obvious missing operations for a decision-support tool, as it explicitly does not execute actions.