jev-mcp
Related Servers
Alternatives to jev-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceProvides coding agents with typed classification, yes/no checks, scoring, ranking, and question-answering tools that return calibrated probabilities for fast, reliable decisions.889 npm44MIT
- AlicenseAqualityCmaintenanceProvides agents with fast, typed, calibrated decision tools for classification, scoring, yes/no checks, and gating risky tool calls.5467 npm2MIT
- AlicenseAqualityCmaintenanceEnables agents to call typed code-review and content-moderation decision tools, returning structured verdicts, probabilities, and confidence-gated actions.2MIT
- AlicenseNot gradedqualityBmaintenanceEnables typed decisions (yes/no, choice, score) with transparent preflight checks, honest confidence reporting, and health monitoring.147 npmApache 2.0
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to submit a state and typed questions and receive structured judgments such as yes/no probabilities, named choices, and rubric scores, with no text generation or parsing.MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to obtain calibrated probabilities, option picks, scale scores, and multi-question judgments for batches of short text, returning numeric results for sorting, filtering, and counting.MIT
TDQS
Scored across 5 tools
Each tool has a clearly distinct purpose: listing models, picking one from a set, scoring on a scale, yes/no checking, and batching multiple independent questions. The descriptions clarify boundaries (e.g., jev_check is specifically for yes/no, while jev_classify handles arbitrary options). No overlap that would cause an agent to misselect.
All tools share the consistent 'jev_' prefix, but the second part is mostly verbs (classify, ask, score, check) except for 'models' which is a noun. This is a minor deviation from a strict verb pattern, but still predictable and readable.
Five tools is well-scoped for a classification/scoring API. Each tool earns its place and covers distinct operations without redundancy. This is within the ideal 3-15 range and appropriate for the server's purpose.
The surface covers the core operations: model discovery, single-label classification, ordered scoring, binary checks, and batched multi-question inference. There are no obvious gaps for the apparent domain; agents can perform all necessary workflows without workarounds.