Skip to main content
Glama
Sign In
agent-eval-policy

agent-eval-policy

by romanfjose
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to agent-eval-policy

No user-submitted related servers found.

    Related Servers

    • APIVouch

      ShahadatTest
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables agents to route goals across multiple independent APIs, enforce constraints, reject invalid evidence, and return verified outcomes with tamper-evident receipts.
      MIT

    • proactive-agent-mcp

      MishaelOliva
      A
      license
      A
      quality
      B
      maintenance
      Enables autonomous AI agents to proactively poll event queues, evaluate document compliance, retrieve grounded knowledge via semantic RAG, enforce human-in-the-loop approval gates, and track multi-model cost budgets.
      10
      MIT

    • Agent QA Harness

      msandroid
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables host coding agents to conduct evidence-first exploratory testing, adversarial review, reproduction, and resumable reporting through immutable job contracts, action budgets, checkpointed ledgers, integrity-checked artifacts, and optional origin-restricted browser automation.
      MIT

    • MangoMe

      tonnestate
      A
      license
      C
      quality
      A
      maintenance
      Persistent multi-agent work graph and document-state machine for contracts, specs, slices, evidence, verification, handoffs, and cost-aware AI execution.
      7
      Apache 2.0

    • Vigil

      leo-bone
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables agents to route every action through a pre-execution gate that returns allow, escalate-to-human, or deny verdicts, backed by deterministic hard-rule blocks plus probabilistic gray-zone scoring, and to run a resumable orchestration loop covering routing, quality gates, stop-loss, acceptance, and escalation. Every decision, arbitration between conflicting agents, and human approval is written to an append-only hash-chained, Ed25519-signed ledger that can be postmortemed, calibrated, alert-scanned, and exported as offline verification bundles or OTel spans.
      1
      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

    A3.5/5.0

    Scored across 3 tools

    Disambiguation4/5

    Each tool targets a distinct phase: seat/budget routing, single-response contract checking, and URL/dossier hygiene. The only wrinkle is dedup_and_lint_dossier bundling two operations with 'and/or' semantics, which could make an agent unsure whether it must supply both inputs.

    Naming Consistency5/5

    All three follow a clean verb_noun (or verb_noun_noun) snake_case pattern: route_agent_seat, evaluate_agent_response, dedup_and_lint_dossier. Predictable and readable throughout.

    Tool Count4/5

    Three tools is thin but matches a narrow policy/eval-enforcement role where each tool is a distinct gate. Nothing feels redundant or padded.

    Completeness3/5

    Covers routing/admission, response validation, and dossier hygiene, but there is no way to inspect or refresh the budget snapshot, enumerate valid roles/contracts, or manage schema definitions—agents hitting an 'unknown role' or 'fails closed' path have no recovery tool.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources