Skip to main content
Glama
serial-mcp

serial-mcp

by alxgmpr

serial_change_settings

Idempotent

Change baud rate, parity, data bits, or stop bits on an open serial session to match a device's UART configuration.

Instructions

Change settings on an open serial 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_change_settings"
  }
}

Input Schema

NameRequiredDescriptionDefault
parityNo
baud_rateNo
data_bitsNo
stop_bitsNo
session_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.0

TDQS

C2.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true, destructiveHint=false, and openWorldHint=true, so the mutation and safety profile is covered. The description adds only the "open serial session" prerequisite. Critically, it does not explain what a null/omitted field means (leave unchanged vs. reset to default), which is the key behavioral question for an all-optional mutation.

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 or redundancy. It is concise but at the cost of substance rather than because it is efficiently complete.

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 five-parameter mutation with no output schema, no parameter documentation, and no annotations describing what changes take effect or when, the description is far too thin. An agent cannot tell whether the session must be idle, whether settings apply immediately, or what a successful response looks like.

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 five parameters, so the description was the only place to explain them and adds nothing. The parameter names are standard serial terminology and enums constrain parity/data_bits, but the null-default partial-update semantics and valid baud/stop-bit ranges remain undocumented.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Change settings on an open serial session" gives a verb (change) and a resource (settings), but "settings" is generic and the description never names what is configurable (baud rate, parity, data bits, stop bits). It also does not distinguish this from siblings like serial_open (which presumably sets initial settings) or serial_set_signals.

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?

The phrase "on an open serial session" implies a prerequisite, but there is no explicit when-to-use guidance, no mention of what to do if no session exists, and no routing to serial_open or serial_set_signals. The agent must infer everything about tool selection.

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