Skip to main content
Glama
serial-mcp

serial-mcp

by alxgmpr

serial_xmodem_send

Destructive

Send a file over a serial connection to UART devices using XMODEM checksum or CRC mode for reliable data transfer.

Instructions

Send 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_send"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeNoxmodem
file_pathYes
session_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.0

TDQS

C2.7/5.0
Behavior2/5

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

Annotations already declare destructiveHint=true, openWorldHint=true and non-idempotent, but the description adds no behavioral context: nothing about blocking duration, timeout/retry behavior, whether an existing remote file gets overwritten, or error handling on checksum failure. For a destructive, likely long-running transfer, that is a real gap, though nothing contradicts the annotations.

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. It is arguably too terse rather than verbose, but every word earns its place and the core action leads.

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?

No output schema, 0% parameter coverage, and only terse annotations for a destructive file-transfer operation that can block for a long time. An agent lacks enough information to call this safely or predict its behavior on failure.

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 three parameters. The description partially illuminates 'mode' ('checksum or CRC'), but says nothing about 'file_path' (local path? format? size limits?) or 'session_id' (default null implies a current/default session, but this is left to inference). With low coverage the description should compensate more than it does.

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 and resource ('Send a file') plus the protocol/mode variant (XMODEM checksum or CRC), which cleanly distinguishes it from the sibling serial_xmodem_receive. It stops short of naming alternatives like serial_write, but the action itself is unambiguous.

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 XMODEM transfer over plain serial_write, no mention that the remote peer must already be in XMODEM receive mode, and no exclusions or prerequisites. The only implied routing is the mode enum, which the schema already carries.

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