Skip to main content
Glama

Related Servers

Alternatives to Lumis

No user-submitted related servers found.

    Related Servers

    • F
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to query and manage a GxP computerized system inventory as a knowledge graph, including blast-radius impact analysis, regulatory lineage, validation-gap detection, audit-trail-compliant status change approvals, and periodic review generation.
      -
    • F
      license
      Not graded
      quality
      C
      maintenance
      Enables fully local retrieval-augmented generation over pharmaceutical sales intelligence, providing MCP tools to search drug labels, clinical trial outcomes, and sales call notes via natural-language queries.
      -
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to discover, risk-assess, request, and track actions on validated BioPharma systems (LIMS, MES, QMS, ELN) without bypassing the validated state, routing each request through GAMP 5 risk classification, ALCOA+ checks, approval workflows, and 21 CFR Part 11 e-signatures. Agents can also retrieve signed, verifiable execution records and audit evidence for the actions they perform.
      Apache 2.0

    TDQS

    A3.6/5.0

    Scored across 13 tools

    Disambiguation4/5

    Most tools have clearly distinct jobs: retrieval (get_country_rules, get_terminology, get_module_mapping, get_gotchas), action-oriented planning (assess_migration_readiness, plan_multi_country_rollout, plan_system_validation), and generic utilities (search_knowledge, compare_entities, traverse_decision_tree). The main blur is that search_knowledge exposes category filters ('country-rules', 'gotchas', 'terminology', 'decision-trees') that substantially overlap with four specialized tools, so an agent could plausibly reach for the wrong one. Descriptions suggest the specialized tools return structured/filtered output, which mitigates but does not eliminate the overlap.

    Naming Consistency5/5

    All 13 names follow a consistent snake_case verb_noun pattern (get_*, run_*, search_*, traverse_*, assess_*, plan_*, compare_*). Verbs are chosen meaningfully rather than arbitrarily, and there are no mixed conventions or versioned/suffixed outliers.

    Tool Count5/5

    Thirteen tools is squarely in the well-scoped range for a knowledge-plus-advisory server, with each tool mapping to a distinct knowledge category or planning task. Nothing feels like filler, and the surface is not so large that selection becomes a burden.

    Completeness4/5

    The read-only advisory surface is well covered: taxonomy discovery, knowledge search, rules/terminology/gotchas retrieval, decision trees, comparison, and three substantive planning tools (migration readiness, rollout waves, CSV). Minor gaps exist — analytical tools default to commercialization areas ('crm', 'safety-pv', 'regulated-content') with no equivalent depth for discovery/clinical, and there is no way to enumerate available decision trees or agent workflows other than via get_taxonomy/get_agent_workflow. These are workable-around rather than blocking.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues