jev-flash-router
Related Servers
Alternatives to jev-flash-router
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables AI coding agents to offload yes/no, multiple-choice, and scoring questions to TypeSafe's Jev, returning compact confidence-scored answers to save tokens and improve speed.1MIT
- FlicenseNot gradedqualityBmaintenanceEnables Claude Code agents to perform structured decision-making through TypeSafe Jev, supporting yes/no checks, route selection, scoring, and batched multi-question judgments with confidence values.1-
- AlicenseAqualityBmaintenanceEnables AI assistants to perform ultra-fast, calibrated decision tasks such as boolean evaluation, category selection, scoring, and batch decisions through TypeSafe AI's Jev model.456 npm1MIT
- AlicenseAqualityCmaintenanceEnables coding or reasoning agents to request structured judgments from TypeSafe's Jev model at decision points, including choices, scores, claim verification, and code reviews, with probabilities and confidence returned as data.59 npmMIT
- AlicenseBqualityCmaintenanceEnables AI agents to obtain typed judgments from TypeSafe's Jev System One models, including yes/no probabilities, multiple-choice selections with distributions, and rubric-based scores, directly usable in code.52AGPL 3.0
- AlicenseBqualityBmaintenanceEnables coding agents to obtain probabilistic decisions from Jev AI via OpenRouter for classification, scoring, and validation, with tools like jev_check, jev_classify, jev_score, and jev_evaluate.53MIT
TDQS
Scored across 1 tool
There is only one tool, so there is no possibility of an agent confusing it with another. Its purpose is stated clearly and does not overlap with anything else in the set.
The single tool name uses a clear snake_case verb_noun format: evaluate_decision. With only one tool there is no broader naming pattern to compare against, so it cannot earn a full 5.
One tool is acceptable for a narrowly scoped decision engine, but the surface feels thin for a server named as a 'router.' It is on the borderline: useful but unlikely to cover a real workflow by itself.
The core evaluation/probability function is present and well described, but there is no follow-up mechanism to apply the decision or inspect routing outcomes. The description implies integration with planning, yet the server stops at returning probabilities.