Skip to main content
Glama
Decision Bridge
by poacosta

Related Servers

Alternatives to Decision Bridge

No user-submitted related servers found.

    Related Servers

    • A
      license
      B
      quality
      B
      maintenance
      Enables MCP clients to evaluate typed choice, score, and noul questions and list available models on configured backends such as Ollama nimble/tev/clef, TypeSafe jev, Kev, or Laya via two stdio tools.
      2
      33 npm
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables MCP-speaking hosts to ask typed questions (yes/no, choice, score) and receive calibrated probabilities instead of prose, over a stdio transport. Runs offline by default with an explicitly disclosed, opt-in egress contract for live providers.
      66 npm
      Apache 2.0
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables MCP hosts to pose typed questions — yes/no, choice, and score — and receive calibrated probabilities instead of prose, over a stdio transport. Runs offline against a synthetic mock by default, with every transmission to a live provider named in a startup egress report.
      66 npm
      Apache 2.0
    • A
      license
      Not graded
      quality
      A
      maintenance
      Exposes three typed-judgment tools over MCP stdio, letting a host ask yes/no, choice, and score questions and receive calibrated probabilities rather than prose. Runs entirely offline against a mock provider by default, with live TypeSafe or OpenRouter routes and a disclosed, per-feature egress contract when explicitly enabled.
      66 npm
      Apache 2.0
    • A
      license
      Not graded
      quality
      A
      maintenance
      Exposes local Ollama as an MCP server so Claude can delegate drafting, summarization, translation, code review, error explanation, model listing, health checks, and file reading to local models via stdio or HTTP.
      517 npm
      1
      Apache 2.0

    TDQS

    A4.2/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools have clearly distinct roles: bridge_status performs only diagnostic checks, while decide runs inference on caller-supplied questions. Their descriptions explicitly separate health/status reporting from decision evaluation.

    Naming Consistency4/5

    Both names use lowercase snake_case and are readable, but the convention is slightly mixed: bridge_status is a noun-like status tool while decide is a bare action verb. The deviation is minor and does not impair understanding.

    Tool Count4/5

    Two tools is slightly under the typical 3-15 range, but the server has a narrow purpose: report bridge health and evaluate supplied questions. Each tool has a clear, essential role rather than feeling arbitrarily thin.

    Completeness4/5

    The core surface is covered: status/diagnostics and the primary decision operation are both present, with detailed limits and error semantics. Minor gaps exist around model/configuration management and explicit model-loading operations, but these are workaroundable through status and the upstream contract.

    Maintenance

    ActivityMaintained
    ResponsivenessSyncing