Skip to main content
Glama
serial-mcp

serial-mcp

by alxgmpr

serial_get_signals

Read-onlyIdempotent

Read the current states of modem-control signals (such as CTS, RTS, DSR, DTR, DCD, RI) from an active serial session to inspect line status and diagnose device handshaking.

Instructions

Read modem-control signal states.

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

Input Schema

NameRequiredDescriptionDefault
session_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.0

TDQS

C2.7/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the description's 'Read' adds nothing beyond the structured safety profile. It does not say whether the read is instantaneous or blocking, whether it flushes buffers, or what happens if the port is closed, all of which are traits annotations cannot express.

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?

One short sentence with no filler, front-loaded with the verb. It is efficient, though the brevity veers into under-specification rather than tightness.

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?

With no output schema, the description carries the burden of saying what comes back, but it never indicates which signals are reported (CTS, DSR, DCD, RI, etc.) or their format. For a hardware-level read tool with one undocumented parameter, this leaves the agent guessing on both input and output.

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% and the single parameter session_id has no documentation anywhere. The description does not explain that session_id is optional, nor what a null value means (default/current session) — a critical ambiguity for a tool that operates on a serial connection.

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?

The description pairs a specific verb ('Read') with a specific resource ('modem-control signal states'), which is enough to distinguish it from the obvious counterpart serial_set_signals in the sibling list. It stops short of naming the sibling as an alternative, but the read/set split is inferable from the text.

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 alternatives such as serial_status or serial_set_signals, and no prerequisites or exclusions are stated. The agent must infer that this is the read-side companion to serial_set_signals from naming convention alone.

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