stm32-stlink-mcp

by phryniszak

Overview Schema Source Related Servers Discussions Admin

TypeScript

Local

Reset the target

debug_reset

Reset an STM32 target via ST-Link debugger, optionally halting or resuming execution after the reset.

Instructions

Resets the target via ST-LINK_gdbserver's monitor reset command, optionally resuming afterward.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "sessionId": "<sessionId>"
    },
    "name": "debug_reset"
  }
}

Input Schema

Name	Required	Description	Default
`halt`	No	Stay halted after reset (default: true — set false to resume immediately)
`sessionId`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 21, 2026

TDQS

A3.6/5.0

Behavior3/5

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

With no annotations, the description carries the full burden. It discloses the underlying mechanism (`monitor reset`) and the optional resume behavior, but it does not explain what happens to the current debug session, whether the target must be connected, or what the command returns. This is more than minimal but not comprehensive.

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 entire description is one sentence that directly states the action and the key option. No filler or redundancy.

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

Completeness3/5

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

The tool is simple, but the description omits any mention of return values or failure modes. It also does not explicitly state that a session must exist, though this is implied by the required `sessionId` parameter. Given no output schema, more detail would be helpful, but the core action is described.

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

Parameters2/5

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

The schema provides descriptions for only one of two parameters (halt), and the description adds no new detail about `sessionId`. The phrase 'optionally resuming afterward' restates the halt parameter’s meaning already present in the schema. With 50% schema coverage, the description should compensate but does not explain the required `sessionId`.

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 'Resets' followed by the resource 'the target' and names the underlying command (ST-LINK_gdbserver's 'monitor reset'). This clearly distinguishes it from sibling tools such as debug_run, debug_halt, and debug_step.

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?

The description does not explicitly state when to use this tool versus alternatives. It implies the purpose but lacks explicit guidance on prerequisites (e.g., active session) or situations where a different tool (e.g., debug_halt) would be more appropriate.

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