Serial MCP Server

Overview Schema Source Related Servers Discussions Admin

serial.set_rts

Set the RTS (Request To Send) control line on a serial connection. Use when device protocol requires manual RTS control.

Instructions

Set the RTS (Request To Send) control line. Usage is device-specific — check the protocol spec or ask the user.

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": {
      "connection_id": "<connection_id>",
      "value": "<value>"
    },
    "name": "serial.set_rts"
  }
}

Input Schema

Name	Required	Description	Default
`connection_id`	Yes
`value`	Yes	True = high, False = low.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0May 29, 2026

TDQS

B3.1/5.0

Behavior2/5

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

With no annotations, the description must cover behavioral traits. It states a write operation ('Set') but does not disclose potential side effects, required permissions, or conditions under which the operation might fail. The device-specific warning is helpful but insufficient.

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

Conciseness5/5

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

Two short sentences, front-loaded with purpose ('Set the RTS control line'), and no redundant information. Highly efficient.

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

Completeness3/5

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

For a simple tool with two parameters and no output schema, the description is adequate but lacks details about error handling, idempotency, or what happens when the line is already in the requested state. The device-specific warning compensates slightly.

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 50% (only the 'value' parameter has a description). The tool description adds no extra meaning about parameters like connection_id or valid values beyond the schema's 'True = high, False = low.'

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 clearly states the action ('Set the RTS control line') and identifies the resource. It does not differentiate from sibling tools like serial.pulse_rts or serial.set_dtr, but the purpose is still clear.

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 description advises that usage is device-specific and to check the protocol spec or ask the user, implying caution. However, no explicit guidance on when to use this tool versus alternatives like serial.pulse_rts is provided.

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