Skip to main content
Glama
Sign In
smolmux

smolmux

by magnusmalm
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

serial_get_incidents

Read-only

List anomalies detected in serial output—kernel panics, faults, watchdog, brownouts, resets—with match and pre-context to diagnose boot stalls or waits that abort.

Instructions

List anomalies the broker detected in output (kernel panic, oops, hard fault, assert, watchdog, brownout, ESP resets, plus profile patterns) with the match and pre-context. Use when a boot stalls, a wait aborts, or output looks like a crash; pair with serial_output_history for the surrounding log.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "serial_get_incidents"
  }
}

Input Schema

NameRequiredDescriptionDefault
secondsNoIf > 0, only return incidents from the last N seconds.

Output Schema

NameRequiredDescriptionDefault
countYes
incidentsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "count": {
+      "type": "integer"
+    },
+    "incidents": {
+      "items": {
+        "properties": {
+          "incident_id": {
+            "type": "string"
+          },
+          "match_text": {
+            "type": "string"
+          },
+          "pattern_name": {
+            "type": "string"
+          },
+          "pre_context": {
+            "type": "string"
+          },
+          "severity": {
+            "type": "string"
+          },
+          "timestamp": {
+            "type": "number"
+          }
+        },
+        "required": [
+          "pattern_name",
+          "severity",
+          "timestamp",
+          "match_text",
+          "pre_context"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "count",
+    "incidents"
+  ],
+  "type": "object"
+}
  2. First observedv0.4.0

TDQS

A4.5/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so safety is covered. The description adds meaningful behavior beyond that: it specifies the detector's classification taxonomy and that each result carries the match plus pre-context, which tells the agent what a returned incident contains. It does not disclose limits on the detection window or buffering, keeping it short of a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences with no filler: the first front-loads what is detected and what each result includes, the second front-loads when to use it and what to pair it with. Every clause earns its place by aiding selection or interpretation.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present, return formatting need not be explained, and the description still covers detection scope, trigger conditions, and sibling pairing. For a single-optional-parameter read tool, nothing an agent needs to select or invoke it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100% and there is only one optional parameter ('seconds'), which the schema already documents fully. The description adds no extra syntax, default, or format detail about that parameter, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('List anomalies the broker detected in output') and enumerates exactly what counts as an anomaly (kernel panic, oops, hard fault, assert, watchdog, brownout, ESP resets, profile patterns). It also distinguishes itself from the sibling serial_output_history by framing that tool as the source of surrounding log context.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives concrete triggering conditions ('when a boot stalls, a wait aborts, or output looks like a crash') and explicitly routes the agent to pair with serial_output_history for surrounding logs. The when-to-use condition and the relationship to the alternative are both stated directly.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools