Skip to main content
Glama
Sign In
zigmo

zigmo

by unprimathe
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to zigmo

No user-submitted related servers found.

    Related Servers

    • slh-server

      alexmerced-oss
      A
      license
      A
      quality
      C
      maintenance
      Enables AI agents to list metrics and dimensions, inspect definitions, and run governed metric queries against Apache Iceberg tables through a semantic layer, without writing SQL or accessing raw rows or columns outside their role.
      5
      Apache 2.0

    • Semantix

      Oroboros26
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to retrieve governed business metric definitions and compiled SQL through MCP-style tools, so they can query consistently under their own read-only roles without guessing joins or metric logic.
      MIT

    • io.github.WiliamRosa/cosmos

      WiliamRosa
      A
      license
      B
      quality
      B
      maintenance
      Enables AI agents to discover governed business concepts and request deterministic metrics with expanded formulas, rules, row filters, reference dates, and evidence instead of writing SQL against raw tables. It keeps personal data from agents and serves the same metric consistently across multiple databases.
      5
      Apache 2.0

    • governed-analytics-agent

      Binary-yev
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables agents to answer analytics questions with provable correctness by resolving metrics through the semantic layer, tracing lineage, traversing knowledge graphs, checking freshness, and searching glossary definitions, while enforcing access controls and logging every call.
      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

    A3.7/5.0

    Scored across 4 tools

    Disambiguation4/5

    The four tools target distinct stages: discovery (list_metrics), definition (describe_metric), execution (query_metrics), and dry-run inspection (explain_query). list_metrics vs describe_metric and query_metrics vs explain_query share the same domain and arguments, so there is mild potential for confusion, but the descriptions clearly separate 'list all', 'explain one', 'run', and 'don't run'.

    Naming Consistency5/5

    All four names follow a clean verb_noun snake_case pattern (list_metrics, describe_metric, query_metrics, explain_query). The only deviation is describe_metric using the singular 'metric' while others are plural, which is a natural, readable choice rather than an inconsistency.

    Tool Count4/5

    Four tools is a tight, well-scoped surface for a metrics/semantic-layer server: discover, describe, query, and preview. It is slightly lean, with no separate tool for browsing dimensions or filters, but every tool earns its place and nothing is redundant.

    Completeness4/5

    The read lifecycle is fully covered—discovery, definition, querying with dimensions/filters/date ranges, and an explain/dry-run path that complements execution. Minor gaps exist (no standalone dimension listing and no validation-only or saved-query operations), but agents can work around these via list_metrics and explain_query.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Resources