Skip to main content
Glama
clira-dev

ezstat-mcp-server

by clira-dev

Related Servers

Alternatives to ezstat-mcp-server

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      C
      maintenance
      Connects AI assistants to Warpmetrics telemetry data to monitor AI agent performance, execution runs, and LLM costs. It allows users to query success rates, latency, and spend metrics directly through natural language interfaces.
      20
      23 npm
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Provides stateful counter tools for AI assistants, enabling accurate counting and tracking of metrics via tag-based or direct tool calls.
      7
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to interact with Datadog's observability platform via natural language, covering metrics, logs, APM, monitors, dashboards, incidents, and infrastructure.
      715 npm
      1
      MIT
    • F
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to analyze text and retrieve real-time system metrics such as CPU, memory, and uptime through LangChain tool calling, with an embedded web UI for testing queries and viewing tool execution logs.
      -

    TDQS

    A4.2/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool has a clear, distinct role: track_metric writes, read_stat does structured reads of a single metric, ask_ezstat handles free-form natural-language queries, and list_stats discovers available metrics. The overlap between read_stat and ask_ezstat is explicitly addressed in their descriptions, making misselection unlikely.

    Naming Consistency4/5

    Most tools follow a clear verb_noun pattern: track_metric, read_stat, list_stats. ask_ezstat also follows verb_noun but uses a product-specific noun, which is slightly inconsistent with the generic metric-related nouns used elsewhere. Overall the pattern is still predictable and readable.

    Tool Count4/5

    Four tools is on the smaller side but appropriate for the focused scope of tracking and querying metrics. Each tool serves a core need without redundancy, though the set could be expanded with e.g. delete_metric or batch operation tools.

    Completeness4/5

    The tool surface covers the essential lifecycle: record (track_metric), read single (read_stat), query over many (ask_ezstat), and discover (list_stats). It lacks explicit update/delete operations, but for a metrics tracking server these are often unnecessary, and agents can work around this limitation.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues