ai.dxpert/uns-tools

transcript

Download complete transcript

stdin:
{"id":1,"jsonrpc":"2.0","method":"initialize","params":{"capabilities":{},"clientInfo":{"name":"toolwitness","version":"s772-v0"},"protocolVersion":"2025-11-25"}}
{"jsonrpc":"2.0","method":"notifications/initialized"}
{"id":2,"jsonrpc":"2.0","method":"tools/list","params":{}}

stdout:
{"jsonrpc":"2.0","id":1,"result":{"protocolVersion":"2025-11-25","capabilities":{"tools":{}},"serverInfo":{"name":"@dxpert/uns-tools","version":"0.1.2"}}}
{"jsonrpc":"2.0","id":2,"result":{"tools":[{"name":"lint_sparkplug_topic","description":"Validate one or more MQTT topic strings against the Sparkplug B topic grammar (Sparkplug 3.0). Free, no API key, no account: the grammar runs locally inside this server and nothing is sent anywhere. Call this whenever a topic that is meant to be Sparkplug appears in a config, a broker trace, a code review, or a user question -- it is faster and far more reliable than reasoning about the grammar from memory. It checks the spBv1.0 namespace level, the eight message types (NBIRTH/NDEATH/DBIRTH/DDEATH/NDATA/DDATA/NCMD/DCMD) plus STATE, node-vs-device level count, the legacy Sparkplug 2.2 STATE form, publish-side MQTT wildcards, empty levels, and identifier characters that break downstream consumers. It returns ordered findings (fail / warn / pass / info) with the parsed topic parts, not a yes/no. It does NOT connect to a broker, decode payloads, or check whether the device actually exists.","inputSchema":{"type":"object","additionalProperties":false,"properties":{"topics":{"description":"One topic string, or an array of topic strings. A single string containing newlines is also accepted and split per line.","oneOf":[{"type":"string"},{"type":"array","items":{"type":"string"},"minItems":1}]}},"required":["topics"]}},{"name":"check_uns_namespace","description":"Check a set of Unified Namespace (UNS) topic paths for the convention problems that quietly rot a namespace: inconsistent hierarchy depth, mixed casing styles across segments, whitespace 

Excerpt shown; complete evidence is in the download.

sinkhole log

Download complete sinkhole log

Scope: runtime isolation evidence in runtime/inspect.json.

canary log

Download complete canary log

Outside this listing scope.

scanner output

Download complete scanner output

Outside this listing scope.

normalized text

Download complete normalized text

{"calls": [], "exit_before_cleanup": null, "initialize": {"capabilities": {"tools": {}}, "protocolVersion": "2025-11-25", "serverInfo": {"name": "@dxpert/uns-tools", "version": "0.1.2"}}, "list_change_notifications": 0, "monotonic_seconds": 0.20195368400891311, "outcome": "listed tools offline", "started_utc": "2026-10-17T12:23:42.134840Z", "status": "completed", "tools": [{"description": "Validate one or more MQTT topic strings against the Sparkplug B topic grammar (Sparkplug 3.0). Free, no API key, no account: the grammar runs locally inside this server and nothing is sent anywhere. Call this whenever a topic that is meant to be Sparkplug appears in a config, a broker trace, a code review, or a user question -- it is faster and far more reliable than reasoning about the grammar from memory. It checks the spBv1.0 namespace level, the eight message types (NBIRTH/NDEATH/DBIRTH/DDEATH/NDATA/DDATA/NCMD/DCMD) plus STATE, node-vs-device level count, the legacy Sparkplug 2.2 STATE form, publish-side MQTT wildcards, empty levels, and identifier characters that break downstream consumers. It returns ordered findings (fail / warn / pass / info) with the parsed topic parts, not a yes/no. It does NOT connect to a broker, decode payloads, or check whether the device actually exists.", "inputSchema": {"additionalProperties": false, "properties": {"topics": {"description": "One topic string, or an array of topic strings. A single string containing newlines is also accepted and split per line.", "oneOf": [{"type": "string"}, {"items": {"type": "string"}, "minItems": 1, "type": "array"}]}}, "required": ["topics"], "type": "object"}, "name": "lint_sparkplug_topic"}, {"description": "Check a set of Unified Namespace (UNS) topic paths for the convention problems that quietly rot a namespace: inconsistent hierarchy depth, mixed casing styles across segments, whitespace in segments, case-collisions between siblings that read as one node but are two, duplicate paths, empty levels, and st

Excerpt shown; complete evidence is in the download.