Skip to main content
Glama
Sign In
mcu-debug-mcp

mcu-debug-mcp

by stillsurge
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

serial_list

List available serial ports, identify common USB-to-serial chips (CH340/CP2102/FT232), and recommend drivers when a board is missing from the port list.

Instructions

列出系统可用串口。识别 CH340/CP2102/FT232 等常见 USB 转串口芯片并给驱动建议。 毕设学生"串口列表里找不到板子"时先调这个。

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "serial_list"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

No annotations are provided, so the description carries the burden — and it discloses non-obvious behavior: the tool not only enumerates ports but also probes chip identity and emits driver recommendations. It is implicitly a non-destructive read, though that is never stated outright.

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?

Three compact sentences, front-loaded with what it lists, then the value-add, then the call trigger. No filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Zero parameters, an output schema that covers return values, and a simple read operation — the description supplies exactly what an agent needs to select and invoke it correctly, with the extra chip/driver detail as a bonus.

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

Parameters4/5

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

The tool takes zero parameters, so there is nothing to misinterpret; baseline 4 applies. Schema coverage is 100% and no parameter semantics are needed.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb+resource (列出系统可用串口) and then extends it with concrete added capability — recognizing CH340/CP2102/FT232 USB-serial chips and suggesting drivers. This cleanly distinguishes it from sibling read/write tools like serial_open, serial_read, and driver_list.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit trigger scenario: 'when the board is not visible in the serial port list, call this first.' That is a real when-to-use cue, but no alternatives or exclusions are named (e.g., when to prefer driver_list or probe_list instead).

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

Deploy Server

Other Tools