Skip to main content
Glama
serial-mcp

serial-mcp

by alxgmpr

serial_xmodem_receive

Destructive

Receive files over a serial connection using XMODEM checksum or CRC mode, with configurable timeout and session support for microcontroller, router, modem, or embedded device transfers.

Instructions

Receive a file with XMODEM checksum or CRC mode.

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": {
      "file_path": "<file_path>"
    },
    "name": "serial_xmodem_receive"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeNoxmodem
timeoutNo
file_pathYes
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?

The description is functional, stating the modes, but doesn't add much to the behavioral understanding beyond what the annotations already provide (like destructiveHint: true). It does not elaborate on specific state transitions or failure modes.

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?

It is extremely concise, consisting of a single sentence that efficiently covers the tool's core functional scope without unnecessary jargon or fluff.

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?

Given the complexity of having four parameters (including session ID and timeout) and the fact that schema description coverage is zero, the description is highly incomplete. It fails to explain the operational context of the file receiving process.

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%. While the description mentions the `mode` parameter, it gives no information about the purpose of `file_path`, `timeout`, or `session_id`. It does not compensate for the massive lack of structured data documentation.

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 defines the tool's action—receiving a file—and specifies the protocols it handles (XMODEM or CRC mode). This clearly distinguishes it from other general serial read tools available in the sibling list.

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 description fails to provide any guidance on when to use this specific tool versus a general `serial_read` or `serial_execute` tool from the sibling list. It offers no context or prerequisites for its usage.

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