Skip to main content
Glama
serial-mcp

serial-mcp

by alxgmpr

serial_write_hex

Transmit raw hexadecimal bytes to a serial device to send binary commands or data over a specified session.

Instructions

Write raw bytes supplied as hexadecimal.

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": {
      "hex_string": "<hex_string>"
    },
    "name": "serial_write_hex"
  }
}

Input Schema

NameRequiredDescriptionDefault
hex_stringYes
session_idNo

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=false, openWorldHint=true and destructiveHint=false, so the write semantics are covered structurally. The phrase 'raw bytes' adds a little context (no framing/terminator is implied), but the description says nothing about bytes written, what happens on malformed hex, or whether input is buffered.

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 short sentence with the verb and key qualifier front-loaded and zero filler. It is efficient, though the brevity is under-specification rather than true density.

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 2-parameter mutation tool with no output schema and zero schema descriptions, the definition leaves the critical unknowns unanswered: hex string format, session_id semantics/default behavior, and what the call returns (byte count? error?). Annotations cover the safety profile but not invocation details.

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 carries the full burden and only hints that hex_string is hexadecimal — it never states the expected format (case, separators like '0x' or spaces, even-length requirement). session_id is entirely undocumented, and with a null default it is unclear whether omitting it targets the active session.

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 verb ('Write') and a specific resource ('raw bytes supplied as hexadecimal'), which distinguishes it from the sibling serial_write (text) and pairs with serial_read_hex. It does not explicitly name those siblings or state the contrast, so it stops short of a 5.

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 choose this over serial_write, serial_command, or serial_execute, and no prerequisites such as needing an open session. The agent must infer the selection rule from the name alone.

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