jev
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| JEV_PYTHON | Yes | Absolute path to the Python interpreter to run the client. | |
| JEV_SSH_HOST | No | SSH host alias for the remote GPU server. | |
| JEV_SSH_CONFIG | No | Absolute path to the SSH configuration file for remote access. | |
| JEV_REMOTE_ROOT | No | Absolute path to the repository root on the remote server. |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| decideA | Return yes/no (noul), choice or score decisions and elapsed seconds using DiffusionGemma. request.questions maps IDs to {type, instructions, criteria}; choice criteria map names to descriptions or null; score criteria are ordered labels. state is optional evidence; sources_only:true restricts evidence. image/state_files read local files and send them to the configured decision server. Files are not modified. Probabilities are uncalibrated and normalized within the supplied candidates, not factual correctness probabilities. Explain this when asked rather than repeating a disclaimer in every result. |
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
Only one tool exists, so there is no possibility of confusing it with another tool. The tool's single responsibility is clear from its description.
With only one tool, there are no naming inconsistencies to evaluate. The name 'decide' is a simple, verb-based descriptor matching its function.
A single tool feels thin for a server, even though it supports multiple decision types internally. This falls at the low end of the borderline range.
The tool covers yes/no, choice, and score decisions, with evidence and file handling. Minor gaps include lack of server configuration or status inspection, but core decision functionality is well covered.