Skip to main content
Glama
serial-mcp

serial-mcp

by alxgmpr

serial_detect_baud

Idempotent

Probes a serial port across common baud rates and ranks readable responses to identify the correct baud rate.

Instructions

Try common baud rates and rank readable responses.

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": {
      "port": "<port>"
    },
    "name": "serial_detect_baud"
  }
}

Input Schema

NameRequiredDescriptionDefault
portYes
probeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.0

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true and destructiveHint=false, and the description's probing language is consistent with a non-read-only operation that transmits to the device. It does not disclose whether the tool opens/closes the port, whether it disturbs an existing session, or what happens when probe is disabled.

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 repetition. It is efficient, though the terseness leaves the definition under-specified rather than tight.

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 should indicate what a 'ranked readable response' looks like (list of rates plus samples? scores?) and how long probing takes. It also omits port-state requirements and the meaning of probe, leaving significant gaps for a hardware-facing tool.

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%, so the description must carry parameter meaning, and it does not: 'port' is never mentioned and the boolean 'probe' (default true) is entirely unexplained. An agent cannot tell whether probe=true actively transmits or merely listens passively, which is a meaningful behavioral difference.

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 action (try common baud rates) and an output behavior (rank readable responses), which is far more informative than the name alone. It is distinguishable from siblings like serial_change_settings, but never names an alternative, so differentiation is implicit rather than explicit.

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 explicit when-to-use or when-not guidance, and no mention of prerequisites such as whether the port must be closed or already open before probing. The discovery use case is only weakly implied by the verb 'detect'.

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