Skip to main content
Glama
Sign In
smolmux

smolmux

by magnusmalm
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

serial_read

Read-only

Drain and view serial console output buffered in the current MCP session without sending commands. Use it for a quick look after your own command, then switch to serial_output_history for lossless capture.

Instructions

Drain the output this MCP session buffered since the last read, without sending. Quick look after your own command; lossy across turns. Lossless capture: serial_output_history with since_seq. Waiting for known text: serial_wait_for.

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_read"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A4.6/5.0
Behavior4/5

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

Annotations cover the safety profile (readOnly, non-destructive, closed-world), and the description adds genuinely non-obvious behavior beyond them: it consumes/drains the buffer, is lossy across turns, and does not transmit on the port. It omits return formatting and empty-buffer behavior, which is why it is not 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?

Three tight clauses, zero filler, and the core action plus its main caveat ('lossy across turns') are front-loaded before the alternative-tool pointers.

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

Completeness4/5

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

For a no-param, fully annotated read tool with no output schema, the description covers purpose, consumption semantics, and alternatives. Only minor operational details (empty-buffer result, encoding/format of drained output) are absent.

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

Parameters4/5

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

The tool takes zero parameters, so the baseline of 4 applies and there is no schema coverage gap to compensate for. The description adds no parameter detail, but none is needed.

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 ('drain the output this MCP session buffered since the last read') plus the critical scope qualifier 'without sending'. It immediately differentiates itself from siblings by naming what it is not (lossless history, text-waiting).

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 explicit when-to-use ('Quick look after your own command'), an explicit limitation ('lossy across turns'), and routes to the two correct alternatives by name with the parameter that selects them ('serial_output_history with since_seq', 'serial_wait_for'). Nothing is left to inference.

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