Skip to main content
Glama
serial-mcp

serial-mcp

by alxgmpr

serial_set_signals

Idempotent

Set DTR or RTS on an open session.

Instructions

Set DTR or RTS on an open session.

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

Input Schema

NameRequiredDescriptionDefault
dtrNo
rtsNo
session_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.0

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare non-read-only, idempotent, non-destructive, open-world behavior, so the safety profile is supplied. The description adds only the 'open session' precondition and omits behaviorally relevant detail an agent would want: whether a signal left null is unchanged, whether both lines are set atomically, and whether the call can pulse/toggle a line. Useful but thin given the presence of annotations lowers the bar.

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 sound. However, at this length the brevity reflects under-specification rather than disciplined economy – nothing about the parameters or the null semantics is addressed anywhere.

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?

No output schema and three parameters at 0% documentation coverage mean the description is the only source of semantics, and it covers none of them. For a hardware-state mutation tool, an agent is left guessing at null handling and signal polarity, so the definition is incomplete for correct invocation.

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% – the schema only gives titles 'Dtr', 'Rts', 'Session Id' with null defaults. The description does not explain what the booleans mean (assert vs. deassert), what null does (leave unchanged? use default?), or what a null session_id resolves to. With three optional parameters entirely undocumented, this is a real gap.

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?

Uses a concrete verb (Set) on a specific resource (DTR/RTS hardware control lines) scoped to 'an open session'. An agent can distinguish this from the sibling serial_get_signals by direction (set vs. read). It stops short of naming that sibling or describing the broader serial workflow, so it is clear but not maximally differentiated.

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?

The phrase 'on an open session' implicitly signals the prerequisite that serial_open must have run first, but no explicit when-to-use, when-not-to-use, or alternative is given. The agent must infer that this is the counterpart to serial_get_signals rather than being told so.

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