Skip to main content
Glama
Sign In
stmctl-mcp

stmctl-mcp

by Sathvik-smarttrak
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

stm32_reset_mcu

Reset an STM32 microcontroller via SWD by specifying the reset type (hardware, software, or core) to recover from hangs or prepare for flashing.

Instructions

Trigger reset signal on target MCU.

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_reset_mcu"
  }
}

Input Schema

NameRequiredDescriptionDefault
portNoConnection portSWD
reset_typeNoReset type: Hardware Reset (HWrst), Software Reset (SWrst), Core Reset (Crst)HWrst

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are provided, so the description must disclose side effects, but it only says 'trigger reset signal' without explaining consequences like halting execution or affecting the debug connection. The reset_type enum is defined in the schema, but the description adds no behavioral detail.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, lean sentence with no filler words. It is appropriately concise for a simple tool, though it sacrifices some behavioral clarity for brevity.

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 the simple tool, the description does not explain when to use it or what happens after a reset. With no annotations or output schema, the minimal text leaves the agent without enough context for confident invocation.

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 schema provides 100% coverage for both parameters, including descriptions for 'port' and 'reset_type'. The description adds no additional parameter details, so it scores at the baseline of 3.

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 clearly states the action ('Trigger'), the object ('reset signal'), and the target ('MCU'). It distinguishes this tool from siblings like stm32_run_mcu, which is about execution rather than reset.

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?

There is no guidance on when to use this tool versus alternatives, nor any mention of prerequisites or exclusions. The only hint is the tool name, so the agent must infer usage context.

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