Skip to main content
Glama
cckyros

decision-lite

by cckyros
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to decision-lite

No user-submitted related servers found.

    Related Servers

    • decidealot

      psyb0t
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables local typed decision-making over MCP Streamable HTTP, running Laya and Von models to turn arbitrary state into choice, score, and yes/no answers with probabilities.
      3
      Do What The F*ck You Want To Public

    • poordjaevin

      Icaro0310
      A
      license
      Not graded
      quality
      A
      maintenance
      Exposes local MCP tools for typed, calibrated LLM decisions — gating risky actions, yes/no judging, classification, ordinal rating, and multi-question decisions in one pass. Runs on the model Devin's CLI already provides via ACP (or a fully offline local backend), so agents get calibrated confidence with no extra API key, no Ollama, and no waitlist.
      1
      MIT

    • openjev-router

      ChristofMilius
      A
      license
      A
      quality
      B
      maintenance
      Provides agents with MCP tools for typed probabilistic decisions—Choice, Noul, and Score—with calibrated probabilities and abstention, using local OpenAI-compatible models via LM Studio logprobs.
      4
      1
      MIT

    • laya-mcp

      PerryLink
      A
      license
      Not graded
      quality
      A
      maintenance
      Provides an MCP interface to the Laya decision model, enabling typed queries (yes/no, multiple choice, score) with preflight token-budget reporting, honest confidence calibration, and structured error handling.
      128 PyPI
      1
      Apache 2.0

    • mcp-confidence

      shaxzodbek-uzb
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables LLM agents to route responses as accept, verify, or ask-a-human based on token logprobs, and provides an MCP server for delegating generation to local models with confidence bands.
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.7/5.0

    Scored across 3 tools

    Disambiguation5/5

    The three tools map cleanly to distinct phases: making a decision (evaluate), providing feedback (record_outcome), and inspecting calibration (decision_stats). There is no overlap in purpose and each has a clearly bounded role.

    Naming Consistency3/5

    evaluate is a bare verb, record_outcome is verb_noun, and decision_stats is a noun phrase, so conventions are mixed. Each name is still readable and self-explanatory, but there is no single predictable pattern.

    Tool Count5/5

    Three tools form a tight, complete decision-calibration loop with no filler. The count is well matched to the narrow stated purpose.

    Completeness4/5

    The evaluate/record_outcome/decision_stats cycle covers the core lifecycle of making, labeling, and auditing decisions. Minor gaps exist (e.g., no way to list or retrieve past evaluate calls), but essential workflows are covered.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources