Skip to main content
Glama
alchemist-s

Zone Two

by alchemist-s
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to Zone Two

No user-submitted related servers found.

    Related Servers

    • garmin-mcp

      shawnduggan
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to query live Garmin Connect health and fitness data, including daily metrics, activities, sleep analysis, and trends via natural language.
      MIT

    • GC-MCP

      macakdev
      F
      license
      Not graded
      quality
      B
      maintenance
      Enables AI assistants to access and query Garmin Connect health and fitness data, including sleep, HRV, training load, and activities, with an optional coaching plugin for personalized training plans.
      3 npm
      4
      -

    • garmin-mcp

      srichards2103
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to retrieve and discuss personal fitness activities, training splits, heart-rate zones, and daily health metrics from a Garmin Connect account.
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3/5.0

    Scored across 35 tools

    Disambiguation4/5

    Each tool targets a distinct Garmin data source or action, and the metric tools are clearly separated by health domain. The main ambiguity risk is between rollups like garmin_briefing and garmin_daily_summary, and between activity list variants, but the descriptions are specific enough to resolve those.

    Naming Consistency4/5

    The garmin_ prefix and snake_case style are consistent throughout. Reader tools use noun-ish names like garmin_hrv and garmin_steps while action tools use verb_noun names like create_workout and delete_workout; a few outliers like garmin_api_get and garmin_whoami break the pattern but are still predictable.

    Tool Count2/5

    35 tools is well over the 25+ threshold and feels heavy for an agent to navigate, even though the domain is broad. Many health metrics and workout operations are legitimately distinct, but the surface would benefit from consolidation, such as grouping daily wellness metrics into fewer tools.

    Completeness4/5

    The set covers the core Garmin wellness and activity domains thoroughly: health metrics, activity history/detail, personal records, training status, and workout lifecycle management. Minor gaps exist, like no update_workout or activity deletion, but garmin_api_get provides a read-only escape hatch and the main workflows have no dead ends.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources