Skip to main content
Glama
Sign In
OpenBaud

OpenBaud

by Leonezz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

list_ports

Read-only

Discover available serial ports and their USB metadata to identify connected hardware, including a built-in mock echo loopback for testing without a device.

Instructions

List serial ports (USB metadata included) plus the always-available mock:echo loopback.

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.3.0

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds real but modest behavioral context: returned results include USB metadata and always contain the mock:echo loopback entry. It says nothing about ordering, sampling, or what happens if no hardware is present.

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?

A single front-loaded sentence with no filler; the resource is stated first and the two payload caveats follow. Nothing is wasted and nothing important is buried.

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 zero-parameter read tool with no output schema and annotations covering safety, the description supplies what an agent needs: what is listed, that USB metadata comes along, and that the mock loopback is guaranteed. Minor gaps remain (no detail on the metadata fields or ordering), but nothing blocks correct invocation.

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, which is the baseline-4 case. The description correctly implies a no-argument, ambient-environment call rather than inviting parameters that do not exist.

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?

Clear specific verb+resource: 'List serial ports'. It even scopes the payload ('USB metadata included') and calls out the always-present mock:echo loopback. It does not name or differentiate itself from likely siblings such as open or ask_port, so it falls short of a 5.

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

Usage Guidelines3/5

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

Usage is only implied: a list-ports tool is obviously a discovery step before opening a connection, and mentioning the always-available mock:echo loopback suggests a no-hardware test path. But there is no explicit when-to-use, when-not-to-use, or named alternative.

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