Skip to main content
Glama

Related Servers

Alternatives to Msty Admin MCP

No user-submitted related servers found.

    Related Servers

    TDQS

    A3.6/5.0

    Scored across 54 tools

    Disambiguation3/5

    Descriptions do heavy cross-referencing ('use X instead') which helps, but the set contains explicitly self-admitted duplicates: get_insights_usage is documented as 'same data as get_model_performance_metrics', and escalate_if_needed is 'the same call' as ask_frontier with a reason field. Overlaps also blur between get_status/get_msty_installation/get_model_providers (ports and paths) and among read_msty_database, list_studio_catalogue and the various list_* tools.

    Naming Consistency4/5

    Nearly all names follow a verb_noun snake_case pattern (list_*, get_*, export_*, import_*, query_*, evaluate_*, suggest_*). The bloom_* domain-prefixed group and noun-first names like bloom_list_behaviors deviate slightly, but the prefix stays predictable and readable.

    Tool Count2/5

    54 tools is well past the point where an agent can reliably select among them, and the count is inflated by aliases and lightly-differentiated variants (two insights tools, two frontier tools, adjacent Bloom history/threshold/handoff tools). The surface spans many sub-domains and would be better split into separate servers.

    Completeness4/5

    Coverage is broad: entity listing and single-row fetch across Studio types, catalogue/counts, pack import/export, gated writes, model install/config/chat, calibration, Bloom evaluation and frontier escalation. Gaps are mainly lifecycle operations — no update or delete for personas, prompts, or tools, and writes are pack-based only — but these are workable around.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues