subq-snap-mcp
Related Servers
Alternatives to subq-snap-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityFmaintenanceLets MCP clients submit a situation and typed questions (yes/no, choice, or scale) to a decision model that returns calibrated probabilities plus an act-or-escalate flag. Enables agents to route, flag, approve, check, or rate cases and hand uncertain ones to a person.373 npmApache 2.0
- AlicenseNot gradedqualityCmaintenanceEnables structured yes/no, multiple-choice, and ordered-score judgments from supplied text and criteria, returning typed probabilities, selected labels, scores, and confidence. It exposes bounded decision tools without search, chat generation, arbitrary HTTP requests, or action execution.219 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables agents to evaluate single records or batches with dynamically authored typed questions, returning structured decisions and probabilities.22 PyPIMIT
- AlicenseAqualityBmaintenanceEnables MCP clients to classify, score, and evaluate content with structured typed decisions via a single generic tool.117 npm2MIT
- AlicenseNot gradedqualityAmaintenanceEnables agents and services to ask small decision models typed questions about text, JSON, images, or video, returning labels, scores, or yes/no answers over MCP tools or a Jev-compatible HTTP API.Apache 2.0
- AlicenseAqualityBmaintenanceLets MCP clients ask typed questions — yes/no, choice, or score — about structured state, including images, and receive calibrated probabilities from System One decision models such as TypeSafe Jev and Cloudflare Clef. Supports TypeSafe, OpenRouter, and local providers selectable per request, with input validation and cost reporting.6219 npmMIT
TDQS
Scored across 5 tools
snap_decide is a batch superset of snap_choice, snap_score, and snap_noul, so for any single-question request two tools are valid selections. The descriptions do clarify the split (batch vs. single typed question) and the three single-question tools are distinct from each other, but the redundancy creates a real selection decision the agent must reason through each call.
All tools share a clean 'snap_' prefix and snake_case, so the set reads as one family. The only wrinkle is that snap_decide/snap_list_models use verbs while snap_choice/snap_score/snap_noul are named after question types rather than actions, a minor convention mix.
Five tools is well-matched to a focused decision-inference API: one per question type, one batch entry point, and one discovery tool. Nothing feels padded and nothing essential is obviously absent.
The surface covers all three question types, a combined multi-question call, and model discovery, which is solid lifecycle coverage for a stateless inference API. Minor gaps: no model-detail/usage or credential-validation tool, and it is unclear how a caller passes a listed model ID into the decision tools, which may be a dead end after snap_list_models.