layajev-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TYPESAFE_API_KEY | No | API key for the Jev (TypeSafe) remote engine. Either this or OPENROUTER_API_KEY can be used to enable the remote Jev backend. | |
| OPENROUTER_API_KEY | No | OpenRouter API key, which can be used as an alternative way to access Jev through OpenRouter. |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| decideA | Choose between several courses of action and get a gated decision. Use when the task is ambiguous: more than one option is plausible, or none clearly is. Returns probabilities over every option plus 'act' or 'escalate' — escalate means it is too close to call and a human or a stronger model should decide. Cheap: a local call costs nothing and no state leaves this machine. |
| decide_manyA | Ask several independent questions about ONE state in a single pass. Question ids stay local, so N questions cost one model call, not N — this is the cheap way to get many judgments at once. Types: 'choice' (label + criteria map), 'score' (ordered list of 2-10 steps), 'noul' (a yes/no, returns P(true)). |
| triage_optionsA | Narrow a LONG list of options and then decide over the survivors. Use when you have more than about twenty candidates: a choice question loses accuracy past that, so this scores them all, keeps the strongest few, and decides over those. The shortlist and what was discarded are both returned, so the cut is visible. |
| judgeA | Ask one yes/no question and get P(true). Use for a risk check with asymmetric costs — 'might this destroy something?', 'is this irreversible?', 'does this violate the contract?' — where the rare yes matters more than the common no. Set the threshold yourself with noul_act_at; it defaults low (0.5). |
| backend_statusA | Which decision engines can run here and why not, if one cannot. Call this first when a decision tool fails: it separates 'the model declined' from 'no engine is installed or configured', which need different fixes. |
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 clearly distinct purpose: backend_status diagnoses engine availability, decide handles general ambiguous choices, decide_many batches independent questions, triage_options narrows large option sets, and judge handles yes/no risk checks. The descriptions emphasize when to use each, making misselection unlikely.
All tool names use snake_case and are concise, but they mix verbs (decide, judge) and nouns (backend_status, triage_options). The pattern is mostly verb-driven, with backend_status being the outlier as a status query, but the style is consistent and readable.
Five tools is well-scoped for a decision-support server. Each tool covers a distinct aspect of the decision lifecycle (status, single decision, batch, triage, binary risk), and none feels redundant or missing.
The surface covers the core decision-making workflow: checking engine availability, making single or batched decisions, handling large option sets, and binary risk assessment. Minor gaps like a history or explanation tool could be added, but the current set is functionally complete for its stated purpose.