Skip to main content
Glama

Related Servers

Alternatives to Verdict

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables agents to evaluate single records or batches with dynamically authored typed questions, returning structured decisions and probabilities.
      22 PyPI
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Crash-test AI agents on real professional decisions. Agents take real tariff classification and patent examination cases, search reference libraries and rulebooks, submit a decision, and get an exact score with a receipt against what the professional actually decided. Most cases were decided after current models were trained.
      9
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to obtain calibrated probabilities, option picks, scale scores, and multi-question judgments for batches of short text, returning numeric results for sorting, filtering, and counting.
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables 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 npm
      MIT
    • A
      license
      A
      quality
      F
      maintenance
      Lets 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.
      3
      73 npm
      Apache 2.0

    TDQS

    B3/5.0

    Scored across 14 tools

    Disambiguation4/5

    Most tools target clearly distinct actions: rubric CRUD/validation, evaluation, multi-subject ranking, human task handling, hub browsing, and calibration. The only real overlap is between check_against_humans (run rubric over a local gold set) and calibration_report (compare decision confidence against human consensus on stored evaluations), which could be confused at a glance despite differing inputs.

    Naming Consistency3/5

    There is a solid verb_noun core (get_evaluation, submit_human_score, validate_rubric, create_rubric, list_rubrics, fork_rubric), but it is mixed with bare verbs (evaluate, compare, reaggregate) and noun-first names (calibration_report, hub_search, hub_get). Readable overall, but no single predictable pattern.

    Tool Count5/5

    Fourteen tools is well within the ideal range and each group (rubric management, evaluation, human tasks, calibration, hub) earns its place in a coherent workflow. Nothing feels padded or redundant at the surface level.

    Completeness3/5

    Rubric lifecycle is only partial: create/list/validate exist but there is no get-by-id, update, or delete for stored rubrics, and the hub surface supports search/get/fork but no publish. Evaluation and human-task workflows look complete, so agents can work around the gaps but with friction.

    Maintenance

    ActivityMaintained
    ResponsivenessOutdated data