Skip to main content
Glama
SkilledDragonCorp

DecisionGate

by SkilledDragonCorp
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to DecisionGate

No user-submitted related servers found.

    Related Servers

    • agent-firewall

      sanskarpal
      A
      license
      A
      quality
      B
      maintenance
      Enables AI agent tool calls to be intercepted and judged before execution, allowing, asking a human, or blocking based on calibrated risk and policy.
      15
      MIT

    • Sentinel

      MikeLegemah5799
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to score their outgoing responses against groundedness and prompt-injection risks mid-turn, returning allow, warn, or block verdicts before the response reaches the user.
      9 npm
      ISC

    • AgentShield

      shima78
      A
      license
      Not graded
      quality
      B
      maintenance
      Enforces configurable policies on AI agent tool calls, allowing, requesting review, or denying actions before they are executed.
      MIT
    • ERDL Guard by OpenOBA

      ERDL Guardofficial

      OpenOBA
      A
      license
      Not graded
      quality
      A
      maintenance
      Enforces deterministic policy decisions on AI agent tool calls, supporting allow, deny, correct, escalate, and human review actions with verifiable audit receipts.
      11 npm
      MIT

    • agent-trust-firewall

      krishnashahane
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to securely invoke tools by enforcing identity proof, capability verification, and risk scoring on every request, blocking unsafe calls before they execute.
      MIT
    Deploy Server
    Context Every Agent Can ShareAgents share what they learn, hand off work, and keep it when you switch models. Start with 5 GB free.fulcradynamics.comAd

    TDQS

    B3.4/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools have clearly distinct purposes: score_tool_call evaluates a proposed tool invocation, while gate_info describes the scorer, thresholds, and evaluation questions. An agent should have no trouble selecting between them.

    Naming Consistency4/5

    Both names use snake_case and are readable, but score_tool_call follows a verb_noun action pattern while gate_info is a noun phrase for metadata. This is a minor convention deviation rather than a confusing inconsistency.

    Tool Count3/5

    Two tools is thin for a server, with only one core functional operation and one informational tool. For a narrowly scoped decision gate this is defensible, but it sits at the lower edge of what feels complete.

    Completeness4/5

    The core gate workflow is covered: score a proposed call and inspect the gate's scorer and thresholds. Minor gaps remain around batch scoring, audit/history, or policy inspection, but agents can work within the current surface.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources