Skip to main content
Glama
serial-mcp

serial-mcp

by alxgmpr

serial_open

Open a serial port session to communicate with UART devices such as microcontrollers, routers, or modems. Configure port, baud rate, parity, data bits, stop bits, and timeouts.

Instructions

Open a serial session. Close it with serial_close when finished.

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

Input Schema

NameRequiredDescriptionDefault
portNo
parityNonone
timeoutNo
baud_rateNo
data_bitsNo
stop_bitsNo
inactivity_timeoutNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.0

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=false, openWorldHint=true and destructiveHint=false, so the safety/mutability profile is covered. The description adds genuinely useful lifecycle context — the session is a resource that must be released via serial_close — but says nothing about port-name formats, behaviour when the port is already held by another session, or whether the open is exclusive/locking.

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

Conciseness4/5

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

Two short, front-loaded sentences with no filler; the action is stated first and the cleanup obligation second. It is efficiently structured, though the extreme terseness is the source of the gaps scored elsewhere.

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?

For a seven-parameter resource-acquisition tool with no output schema and no parameter documentation, the description is well short of complete. Critically, with no output schema an agent is not told that a session handle/identifier is returned and that it must be passed to serial_read/serial_write; nor is the port format or error behaviour on a busy port described.

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 description coverage is 0% across seven parameters, so the description carries the full burden and discharges none of it. Nothing explains the port string format (COM3 vs /dev/ttyUSB0), the units and semantics of timeout versus inactivity_timeout (both numbers with vastly different defaults), or that all parameters are optional.

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 + resource: 'Open a serial session.' An agent can distinguish it from the many serial_* siblings, and it names serial_close as its counterpart. It stops short of clarifying scope (e.g. that it acquires an exclusive handle on a physical port), which would sharpen it against serial_execute/serial_command.

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

Usage Guidelines3/5

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

Provides only lifecycle guidance: close with serial_close when finished. There is no guidance on when to use serial_open versus higher-level siblings like serial_execute or serial_command (which may open implicitly), nor any pre-requisite such as consulting list_serial_ports to discover a valid port. Usage is implied rather than stated.

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