Skip to main content
Glama
ZeroStack RF Diagnostics MCP

ZeroStack RF Diagnostics MCP

Official

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

SMLIGHT ZeroStack (Release Zero (0.9.9-beta.1)) RF & Silicon Diagnostics MCP Server (https://smlight.tech/software/zerostack). Use these read-only tools to diagnose Zigbee2MQTT, Home Assistant ZHA, and OpenThread Border Router logs, decode TI SimpleLink F2 (CC2652P, CC2652P7/CC1352P7, CC2674P10) and Silicon Labs EFR32 registers, evaluate hardware SrcMatch coordinator capacity, and retrieve hardware-verified DWT->CYCCNT and fault-injection benchmarks across SMLIGHT SLZB-06, SLZB-06U, SLZB-06P7, SLZB-06P7U, SLZB-06P7v1, SLZB-07P7, SLZB-06P10, and SLZB-07P10 coordinators.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}

Tools

Functions exposed to the LLM to take actions

NameDescription
analyze_zigbee_thread_logA

Analyze pasted Zigbee2MQTT, Home Assistant ZHA, or OpenThread logs for fault signatures.

When to use:

  • Use this tool when diagnosing runtime error logs, adapter timeouts (SRSP ... after 6000ms), MAC/NWK/APS status codes (0x10, 0x11, 0xc7, 0xcd, 0xe1/225, 0xe9/233, 0xf0/240, 0xf1/241), interview failures (0xa7), or ZCL telemetry/genTime floods.

  • Do NOT use for decoding raw hexadecimal MCU register words (decode_silicon_register), sizing network capacity (check_coordinator_capacity), or querying hardware benchmark tables (get_zerostack_benchmarks).

Behavior:

  • Executes deterministically offline with zero network or serial I/O.

  • Ranks detected faults by severity and root-cause priority (ZNP_SYS_RESET_IND > lockstep timeouts > memory/buffer exhaustion > RF delivery symptoms) and returns stock SDK root causes, immediate workarounds, and SMLIGHT ZeroStack (Release Zero (0.9.9-beta.1)) fixes.

decode_silicon_registerA

Decode a hexadecimal MCU register or radio-core command status word into bitfields.

When to use:

  • Use this tool when inspecting a TI SimpleLink F2 (CMD_IEEE_RX, CMD_IEEE_CSMA, RFC_DBELL, SRCMATCH, VIMS, PRCM, UART0_FR, UART0_RSR, UART0_CTL, IOCFG0..31, AON_PMCTL_RESETCTL), Silicon Labs EFR32 (EUSART0_IF, USART0_IF, USART0_STATUS, EMU_RSTCAUSE), or ARM Cortex-M4/M33 (SCB_CFSR 0xE000ED28, SCB_HFSR 0xE000ED2C) hex register/status value captured from SWD/JTAG, a crash dump, or telemetry.

  • Do NOT use for parsing multi-line host application logs (analyze_zigbee_thread_log) or evaluating mesh node counts (check_coordinator_capacity).

Behavior:

  • Executes deterministically offline with zero hardware or network I/O.

  • Returns decoded bitfield flags, boolean healthy status, root-cause diagnosis, and links to silicon errata notes; raises ValueError on unsupported chip or register_or_addr identifiers or unparseable hex_value strings.

check_coordinator_capacityA

Calculate hardware SrcMatch slot utilization, pendAll threshold, and SRAM heap headroom.

When to use:

  • Use this tool for capacity planning and topology sizing given (device_count, sleepy_zed_count, chip_family) to evaluate 32-slot RFC_RAM SrcMatch exhaustion, pendAll (FP=1) promotion when sleepy_zed_count > 32, indirect queue quota isolation, and SRAM headroom (88 KB / 144 KB / 256 KB).

  • Do NOT use for parsing runtime logs (analyze_zigbee_thread_log), decoding register hex values (decode_silicon_register), or fetching DWT->CYCCNT latency benchmarks (get_zerostack_benchmarks).

Behavior:

  • Executes deterministically offline; derives router_count = device_count - sleepy_zed_count.

  • Raises ValueError if device_count < 0, sleepy_zed_count < 0, sleepy_zed_count > device_count, or chip_family is unrecognized.

get_zerostack_benchmarksA

Retrieve hardware-verified DWT->CYCCNT latency and fault-injection benchmarks by SKU.

When to use:

  • Use this tool to query hardware specifications (CPU, Flash/SRAM, DIO10/DIO11 RTS/CTS wiring, supported baud rates) and cycle-accurate Part 1 execution latencies (TCLK lookup, NWK encrypt/decrypt, routed hop ceiling, O(1) allocator) plus Part 2 adversarial resilience metrics (3,255 MAC vectors, 22,959 brownout cut points, UART framing abuse, 50-router broadcast storms) for an SMLIGHT coordinator model or 'all'.

  • Do NOT use for sizing a user's specific mesh node count (check_coordinator_capacity) or diagnosing pasted log text (analyze_zigbee_thread_log).

Behavior:

  • Executes deterministically offline with zero network or hardware I/O.

  • Raises ValueError if platform does not match a supported SMLIGHT SKU or 'all'.

Prompts

Interactive templates invoked by user choice

NameDescription
diagnose_zigbee_logGenerate a bounded structured prompt for diagnosing Zigbee2MQTT, ZHA, or OTBR logs.

Resources

Contextual data attached and managed by the client

NameDescription
resource_benchmarks_summaryReturn JSON summary of ZeroStack Part 1 & Part 2 hardware benchmarks.
resource_supported_modelsReturn JSON matrix of supported SMLIGHT TI SimpleLink F2 hardware models in Release Zero.
resource_diagnostics_catalogReturn the declarative ZeroStack diagnosticsCatalog.json SSOT.

TDQS

A4.6/5.0

Scored across 4 tools

Disambiguation5/5

Each tool targets a clearly distinct input type and task: numeric capacity sizing, hex register words, pasted runtime logs, and static benchmark lookup. Every description explicitly enumerates what to use it for and names the sibling tools it must not be confused with, leaving essentially no overlap.

Naming Consistency5/5

All four names are snake_case and follow a verb_noun pattern (check_, decode_, analyze_, get_) with domain-specific nouns. No style mixing or vague verbs.

Tool Count5/5

Four tools for a narrow offline RF/Zigbee diagnostics domain, each covering a genuinely separate diagnostic facet (sizing, register decode, log triage, benchmarks). Nothing redundant and nothing that feels like padding.

Completeness4/5

The surface covers the main offline diagnostic workflows — capacity planning, silicon register decoding, log fault triage, and hardware benchmarks — with no dangling cross-references. Minor gaps remain, such as firmware/config compatibility validation or any live serial/ZNP command inspection path, which agents would have to work around manually.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues