Skip to main content
Glama
73882

feature-separate-batch-eval-mcp

by 73882

Related Servers

Alternatives to feature-separate-batch-eval-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables conversational patent data analysis through a set of tools for trend analysis, clustering, word cloud generation, and more. Allows natural language queries to explore patent datasets with structured results and visualizations.
      1
      AGPL 3.0
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables evidence-first game operations incident investigation through read-only MCP tools, including metric queries, cohort comparisons, anomaly detection, and reproducible incident report drafting with citations.
      76
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables analyzing coding-agent session transcripts to measure tool efficiency, detect loops, track test outcomes, and report costs, with MCP tools for listing sessions, analyzing sessions, finding loops, and generating cost reports.
      4
      MIT

    TDQS

    C2.8/5.0

    Scored across 5 tools

    Disambiguation4/5

    Each tool targets a distinct action: status (list cohorts), tag (assign records), check (validate one cohort), run (execute network eval), insights (list persisted results). Status and check both touch 'readiness' and status/insights both list things, which introduces mild overlap, but descriptions keep them separable.

    Naming Consistency4/5

    Every tool shares the consistent 'feature_separate_batch_eval_' prefix followed by a short suffix, forming a predictable pattern. Minor deviation in that tag/check/run are verbs while status/insights are nouns, but overall highly consistent.

    Tool Count4/5

    Five tools is a reasonable, well-scoped set for a batch-evaluation workflow (readiness, tagging, validation, execution, insights). Slightly lean but each tool has a clear role without redundancy.

    Completeness3/5

    The core lifecycle (list readiness, assign cohorts, validate, run, retrieve insights) is covered, but there is no way to modify/remove cohort assignments or clear/export persisted insights, leaving some dead ends.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues