TypedDecisionMCP
Related Servers
Alternatives to TypedDecisionMCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceProcesses large files, error logs, and codebase searches locally via Ollama to reduce token consumption in Cursor by up to 80%.14 npm2MIT
- AlicenseAqualityAmaintenanceEnables routing tasks across Cursor agents and external LLM backends through chat, while managing local models, write allowlists, and asynchronous workflows.354 npm1MIT
- FlicenseNot gradedqualityBmaintenanceLocal-first code retrieval for AI agents — cuts codebase context from thousands of tokens to a few hundred, with zero hallucinated file paths.3-
- AlicenseNot gradedqualityBmaintenanceEnables autonomous context window management, prompt caching, token optimization, and real-time observability for AI coding agents across multiple IDEs, reducing token costs and improving performance.MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI coding agents to quickly find relevant code, focus reads on important parts of large files, and pick relevant items from long lists, reducing token usage and search time.2MIT
- AlicenseCqualityCmaintenanceEnables local-first model routing and persistent tool library management, allowing automated workflow detection and conversion of stable patterns into reusable tools.40Mozilla Public 2.0
TDQS
Scored across 1 tool
With only one tool, there is no possibility of confusion or misselection between tools. The single tool 'decidir' is unique, so disambiguation is trivially perfect.
The tool name 'decidir' is a clear, single verb, and since there is only one tool, there is no naming pattern to violate. It is slightly inconsistent with typical verb_noun conventions, but internally consistent and readable.
The server has only one tool that handles a wide range of presets (comando, subagente, diff, etc.), making it a monolith. This is too few tools for the apparent scope, as an agent would need to parse presets and cannot use distinct tools for different decision types.
The single tool covers only a generic 'decide' operation with presets, but lacks any other operations like listing available presets, getting metadata, or handling workflow-specific actions. There are significant gaps that would limit an agent's ability to perform complex tasks without workarounds.