Skip to main content
Glama
serial-mcp

serial-mcp

by alxgmpr

serial_wait_for

Waits for a regex pattern in incoming serial output, then optionally sends a response; configure timeout, encoding, and max output bytes to monitor device communication.

Instructions

Wait for a regex in incoming output, optionally responding on match.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "pattern": "<pattern>"
    },
    "name": "serial_wait_for"
  }
}

Input Schema

NameRequiredDescriptionDefault
patternYes
respondNo
timeoutNo
encodingNoutf-8
session_idNo
respond_hexNo
max_output_bytesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.8.0
    • addedInput schema / properties / max_output_bytes
      Added value: +{
      +  "default": 16384,
      +  "title": "Max Output Bytes",
      +  "type": "integer"
      +}
  2. First observedv0.6.0

TDQS

C2.6/5.0
Behavior2/5

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

Annotations declare readOnlyHint=false, openWorldHint=true and idempotentHint=false, and the description does hint at the write side effect via 'optionally responding on match.' However, the critical behavior of a blocking wait is undisclosed: whether it errors or returns empty on timeout, whether matched output is consumed from the buffer, and whether output is truncated.

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

Conciseness3/5

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

A single front-loaded sentence with no filler, which is structurally good. But for a 7-parameter blocking tool, one sentence is under-specified rather than genuinely concise.

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

Completeness2/5

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

A blocking, state-mutating serial operation with 7 parameters, no output schema, and no annotation detail beyond safety hints needs substantially more: timeout semantics, buffer consumption, default session resolution, and return shape all remain unexplained.

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

Parameters2/5

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

Schema coverage is 0% across 7 parameters, yet the description only touches two of them implicitly (pattern and respond). Timeout behavior, encoding, session_id resolution, respond_hex, and max_output_bytes truncation are completely undocumented anywhere.

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

Purpose4/5

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

States a specific verb and resource: it waits for a regex pattern in incoming serial output, with an optional response on match. That is far more informative than the name alone, but it does not distinguish this blocking tool from siblings like serial_read or serial_read_since, which an agent could plausibly confuse it with.

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

Usage Guidelines2/5

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

There is no guidance on when to use this instead of serial_read, serial_read_since, or serial_execute, and no mention of prerequisites such as an open session. The agent must infer that this is the blocking variant from the name alone.

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