Skip to main content
Glama
serial-mcp

serial-mcp

by alxgmpr

serial_send_break

Sends a serial break signal to a connected device for a set duration, useful for UART line control, resets, or signaling without closing the session.

Instructions

Send a serial break signal.

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

Input Schema

NameRequiredDescriptionDefault
durationNo
session_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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 already declare a mutating, non-idempotent, open-world operation with destructiveHint=false, so the safety profile is partially covered. The description adds nothing about what a break signal does to the connected device (interrupting transmission), whether it affects buffered data, or how duration is applied.

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?

A single front-loaded sentence with no filler, and it is easy to scan. Its brevity is offset by under-specification, but the sentence itself is efficiently constructed.

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 state-changing serial operation with no output schema and zero-parameter documentation, the description leaves the agent without the targeting (session_id) or timing (duration) needed to call it correctly. Given identifier-free parameters with null defaults, an agent cannot know which session is affected.

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

Parameters1/5

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

Schema description coverage is 0% and the two parameters are undocumented. The description does not mention 'duration' (a fractional-second value with a default) or 'session_id' (which session receives the break), so neither meaning nor defaults are clarified 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 ('Send') and resource ('serial break signal'), which is clear and unambiguous. It does not differentiate from nearby siblings such as serial_set_signals or serial_write, so an agent must infer which means 'break'.

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 versus serial_set_signals, serial_write, or serial_close. The only implied context is that a session must already be open, which is not stated.

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