Skip to main content
Glama
serial-hub-mcp

serial-hub-mcp

by yhuan416

列出串口

list_ports

Enumerate serial ports detected on the system, returning path, vendor, serial number, and USB VID/PID. Call before opening a port to confirm which ports exist.

Instructions

枚举系统检测到的串口。返回每个端口的路径、厂商、序列号、USB VID/PID 等。打开前先调用此工具确认存在的端口。

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": "list_ports"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full burden. It communicates that this is a detection/enumeration operation and names key return fields, but it does not explicitly state read-only/no-side-effect behavior, result ordering, or what happens when no ports are found.

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 short sentences, front-loaded with what is enumerated and returned, followed by the pre-open usage instruction. Every sentence adds useful information with no filler.

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

Completeness4/5

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

For a simple zero-parameter read-only listing tool, the description is largely complete: it explains the purpose, key returned fields, and the pre-open workflow. Because there is no output schema, the description carries return-value explanation, and the trailing 'etc.' leaves the exact result shape slightly open.

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 has zero parameters, so the schema carries no parameter semantics. The description adds nothing misleading and correctly frames the tool as taking no selection or filtering input.

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?

The description uses a specific verb/resource: enumerate system-detected serial ports, and explicitly lists returned fields such as path, vendor, serial number, and USB VID/PID. The clause about calling it before opening distinguishes it from the sibling `open` without opening either schema.

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?

It clearly tells the agent when to use the tool: before opening a port, to confirm which ports exist. It does not state explicit exclusions or alternatives beyond the implied relationship with `open`, so it is strong but not fully exhaustive.

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