Skip to main content
Glama
kkst1

Board Terminal Skill

by kkst1
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Board Terminal Skill

MCP server exposing one tool, board_terminal, for running shell commands on a Linux development board through a controlled executor.

The first backend is UART serial. SSH is represented by a placeholder interface so it can be added without changing the MCP tool contract.

Tool

Input:

{
  "command": "cat /proc/cpuinfo"
}

Output:

{
  "success": true,
  "stdout": "processor : 0\n...",
  "stderr": "",
  "exit_code": 0,
  "elapsed_ms": 135
}

For serial shells there is no reliable process exit status unless the command wrapper reports it. This implementation wraps every command and captures a marker containing $?, so exit_code is the command exit code when the shell supports standard POSIX syntax. If the marker cannot be parsed but the prompt returns, exit_code defaults to 0.

Related MCP server: serial-mcp

Configuration

Environment variables:

Variable

Default

Description

BOARD_BACKEND

serial

Backend name. Currently only serial is implemented.

BOARD_SERIAL_PORT

COM3

Serial device path, for example COM3 or /dev/ttyUSB0.

BOARD_SERIAL_BAUDRATE

115200

UART baud rate.

BOARD_SERIAL_TIMEOUT

0.2

Per-read timeout in seconds.

BOARD_COMMAND_TIMEOUT

15.0

Command completion timeout in seconds.

BOARD_PROMPT

<<<PROMPT>>>

Stable shell prompt used to detect completion.

BOARD_ENCODING

utf-8

Serial text encoding.

Run

Install dependencies:

python3 -m pip install -e .

Start the MCP server over stdio:

board-terminal-skill

Example MCP client configuration:

{
  "mcpServers": {
    "board-terminal": {
      "command": "board-terminal-skill",
      "env": {
        "BOARD_SERIAL_PORT": "/dev/ttyUSB0",
        "BOARD_SERIAL_BAUDRATE": "115200"
      }
    }
  }
}

Available Tools

1 tool
board_terminalC

Run a shell command on the connected Linux development board.

ParametersJSON Schema
NameRequiredDescriptionDefault
commandYes

Output Schema

ParametersJSON Schema
NameRequiredDescription

No output parameters

TDQS

C2.4/5.0
Behavior1/5

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

No annotations are provided, so the description carries full burden for behavioral disclosure. It only states 'Run a shell command,' omitting critical details such as destructive potential, output format, timeout behavior, or authentication needs for a terminal command runner.

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?

The description is a single, clear sentence with no unnecessary words. It is appropriately concise for a simple tool with one parameter.

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?

Despite low complexity (1 parameter, no nested objects), the description does not cover return values or side effects, even though an output schema exists. The absence of behavioral context makes it incomplete for an agent to use safely.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, yet the description adds no meaning beyond what the parameter name 'command' implies. No format, constraints, or examples are given, failing to compensate for the schema's lack of description.

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 states the verb 'run' and the resource 'shell command on connected Linux development board'. It is specific enough to convey the tool's function. With no sibling tools, differentiation is not needed.

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?

No guidance on when or when not to use the tool is provided. There is no mention of prerequisites, safety concerns, or alternatives, leaving the agent without context for appropriate invocation.

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

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 1 tool updatev0.1.0
    • First observedboard_terminal
Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

B3/5.0

Scored across 1 tool

Disambiguation5/5

With only one tool, there is no possibility of confusion or overlap, so disambiguation is perfect.

Naming Consistency5/5

The single tool name 'board_terminal' is clear and follows a consistent style, making it predictable.

Tool Count3/5

One tool is minimal but appropriate for a focused 'Board Terminal Skill' that only needs to run shell commands. However, it is on the thin side.

Completeness4/5

The tool fully covers the stated purpose of running shell commands on a board, with no obvious missing operations for that narrow scope.

Maintenance

ActivityStale
ResponsivenessNo issues

Resources

Related MCP Connectors

Related MCP Servers

  • serial-mcp

    alxgmpr
    A
    license
    A
    quality
    A
    maintenance
    MCP server that lets LLMs talk to serial devices: microcontrollers, routers, modems, embedded Linux, anything with a UART.
    23
    5
    MIT

  • serial-mcp

    davidalo
    F
    license
    A
    quality
    D
    maintenance
    MCP server for serial port communication. Provides tools to open, read, write, and manage serial ports through the Model Context Protocol.
    10
    -

  • BYO Server

    JasonPeng2019
    F
    license
    A
    quality
    B
    maintenance
    Headless local stdio MCP server for board-debug operations, allowing compatible clients to use tools for firmware debugging and board management.
    20
    1
    -