Skip to main content
Glama

Related Servers

Alternatives to lodestar

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      C
      maintenance
      Enables an AI assistant to answer customer-success questions by synthesizing simulated billing, support ticket, and product usage data into composite churn-risk scores, bands, and plain-language explanations for fictional accounts. It exposes raw-data tools, a synthesis tool, and a methodology resource so users can list at-risk accounts or get a per-account health summary.
      4
      MIT
    • F
      license
      B
      quality
      B
      maintenance
      Exposes client health data through a consolidated tool surface covering sleep, exercise, nutrition, cardio, fitness, cognitive, lifestyle, trends, notes, and chat history. Enables LLMs to retrieve time-series vitals, periodic assessments, unstructured text, and rolled-up summaries via standardized envelopes.
      11
      -
    • A
      license
      Not graded
      quality
      A
      maintenance
      Provides read-only access to Churn Solution retention analytics, including cancellation-flow metrics, save rates, recovered revenue, offer performance, cancellation reasons, and customer feedback.
      MIT
    • F
      license
      Not graded
      quality
      B
      maintenance
      Provides read-only tools for analyzing a collections portfolio, including summaries, aging, account details, cashflow, and collector performance, with on-demand HTML reporting via natural language.
      -
    • F
      license
      Not graded
      quality
      C
      maintenance
      Provides read-only operational tools (sales summaries, orders, top customers) over a multi-tenant dataset, with tenant isolation enforced server-side so no tenant parameter appears in the tool schema.
      -

    TDQS

    A3.5/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool returns a uniquely identifiable report or metric type (health, trend, claims, risks, pipeline, actions). No two tools appear to serve the same purpose, and the descriptor nouns clearly delimit their boundaries.

    Naming Consistency5/5

    All tool names follow a uniform get_<report_noun> pattern. The naming is predictable and scannable, with no mixing of verb styles or casing conventions.

    Tool Count5/5

    Six tools form a tight, well-scoped set for a read-only analytics reporting server. Each tool earns its place by exposing a distinct report surface without redundancy or bloat.

    Completeness4/5

    The set covers the primary report types implied by the server's purpose: health, trends, claims, risks, pipeline, and actions. A possible minor gap is an all-reports overview or metadata listing, but the core reporting surface feels complete for its domain.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues