Skip to main content
Glama
Sign In
stmctl-mcp

stmctl-mcp

by Sathvik-smarttrak
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

stm32_list_probes

List all connected ST-LINK debug probes, J-Link programmers, USB bootloaders, and COM serial ports to identify available interfaces for STM32 flashing and debugging.

Instructions

List all connected ST-LINK debug probes, J-Link programmers, USB bootloaders, and COM serial ports.

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

Input Schema

NameRequiredDescriptionDefault
interface_typeNoInterface type to scan (default: ALL)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4/5.0
Behavior3/5

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

No annotations are provided, so the description must carry the full burden. It conveys a read-only operation via the verb 'List' and specifies the device types scanned, but it does not disclose prerequisites (e.g., drivers), return format, or behavior when no devices 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?

The description is a single, information-dense sentence with no redundant words or filler. It covers the full scope of the tool in minimal space.

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 discovery tool with one optional parameter and full schema coverage, the description adequately conveys the core function. However, it lacks explicit mention of output format or error behavior, and no output schema exists to compensate.

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

Parameters3/5

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

The single parameter interface_type is fully documented in the schema with enum values and a description. The tool description adds no additional parameter-level detail, so it does not exceed the baseline set by the high schema coverage.

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 the specific verb 'List' with a clear resource: 'connected ST-LINK debug probes, J-Link programmers, USB bootloaders, and COM serial ports.' This unambiguously identifies the tool as a discovery/enumeration tool and distinguishes it from sibling tools like stm32_flash_firmware or stm32_connect_info.

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?

The description clearly implies the tool is for enumerating connected hardware before other STM32 operations, by listing the specific device types it scans. However, it does not explicitly state when to use this over alternatives or provide any exclusions, so it stops short of a 5.

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