Skip to main content
Glama
gokeshenzhen

io.github.gokeshenzhen/traceweave

by gokeshenzhen
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to io.github.gokeshenzhen/traceweave

No user-submitted related servers found.

    Related Servers

    • rtl-mcp-agent

      cbfaf
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to analyze RTL simulation and synthesis logs through deterministic tools for compile-log summaries, signal tie-off safety checks, and regression result statistics.
      -

    • wavekit-mcp

      cxzzzz
      F
      license
      Not graded
      quality
      B
      maintenance
      An MCP server that provides AI assistants with a persistent, sandboxed Python environment for waveform analysis, enabling loading and manipulation of VCD/FST/FSDB files and temporal pattern matching.
      9
      -

    • Waveform MCP Server

      ynivin
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables analysis of RTL waveform files (VCD, FST) through WAL (Waveform Analysis Language). Supports signal inspection, transition extraction, and advanced waveform queries for hardware design verification.
      16
      BSD 3-Clause

    • mcp-verilog

      zesun33
      A
      license
      A
      quality
      B
      maintenance
      Enables AI coding agents and IDEs to lint, compile, syntax-check, and simulate Verilog/SystemVerilog designs through structured, token-efficient MCP tools with isolated containerized toolchains.
      4
      32 npm
      Apache 2.0
    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.4/5.0

    Scored across 38 tools

    Disambiguation2/5

    Several near-synonymous clusters exist: analyze_failures/analyze_failure_event/recommend_failure_debug_next_steps, get_signal_at_time/get_signal_transitions/get_signals_around_time/get_signals_by_cycle, and trace_signal_path/trace_x_source/explain_signal_driver/find_signal_loads. Long descriptions differentiate them, but the tool set itself does not make the boundaries obvious, so misselection is likely.

    Naming Consistency4/5

    Most tools follow a readable snake_case verb_noun pattern (get_tb_subtree, parse_sim_log, inspect_handshake). Minor inconsistencies: period is a bare noun, cursor_set/list/delete invert the noun-verb order, and singular/plural varies (get_signal_at_time vs get_signals_by_cycle).

    Tool Count2/5

    38 tools is far above the 25+ threshold for a coherent surface. Several families (signal getters, handshake suggestors, failure analyzers) could be consolidated into parameterized tools, making the surface heavier than necessary for an agent to navigate.

    Completeness4/5

    The core hardware-debug lifecycle is well covered: hierarchy build/query, log discovery/parsing/failure comparison, waveform search/sampling, driver/load/path tracing, and handshake/protocol checks. Minor gaps include no source-file content access, no full waveform diff beyond first divergence, and no functional coverage analysis, but these are not blocking for the stated purpose.

    Maintenance

    ActivityActive
    ResponsivenessNo issues

    Resources