Jev Decision MCP
Related Servers
Alternatives to Jev Decision MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceA TypeScript MCP server that enables LLM agents to interact with Atlassian Data Center products (Jira, Confluence, Bitbucket) through typed tools, with tiered operation exposure and safety defaults.9 npmMIT
- AlicenseNot gradedqualityDmaintenanceTurn your typed TypeScript functions into an MCP server — tool, resource, and prompt schemas inferred from your types and JSDoc. No schema library, no decorators, no boilerplate.9 npmMIT
- AlicenseAqualityAmaintenanceA TypeScript MCP server that enables agents to request focused, one-shot consultations with allowlisted Gemini models, with guaranteed model provenance and no silent model changes.2MIT
- FlicenseNot gradedqualityBmaintenanceA TypeScript MCP server with strict schema validation and security guards, currently implementing echo, get_time, hash_text, uuid_generate, and json_validate tools.-
- AlicenseBqualityCmaintenanceA TypeScript-based MCP server that provides tools to interact with local Codex and Gemini CLIs via stdio transport. It enables users to execute prompts through the ask_codex and ask_gemini tools, supporting custom models and timeout configurations.13 npm6MIT
- -licenseNot gradedqualityNot gradedmaintenanceA production-ready TypeScript MCP server providing basic tools (add, echo, timestamp), resources (server info, greetings, data access), and prompt templates (analyze, code-review, summarize). Serves as a foundation for building custom MCP servers with extensible architecture.221 npm-
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.