stm32-stlink-mcp

by phryniszak

Overview Schema Source Related Servers Discussions Admin

TypeScript

Local

Clear a breakpoint

breakpoint_clear

Delete an existing breakpoint by its number to manage debugging sessions on STM32 microcontrollers.

Instructions

Deletes a previously set breakpoint by its number.

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>",
      "breakpointNumber": "<breakpointNumber>"
    },
    "name": "breakpoint_clear"
  }
}

Input Schema

Name	Required	Description	Default
`sessionId`	Yes
`breakpointNumber`	Yes	Breakpoint number as returned by breakpoint_set

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 21, 2026

TDQS

A3.9/5.0

Behavior3/5

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

No annotations, description indicates destructive delete but lacks details on side effects like persistence or error handling.

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?

Short, clear, single sentence with no unnecessary words.

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?

Sufficient for a simple delete operation, but could mention success/failure or that it removes from the breakpoint list, though not critical.

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?

SessionId is not described in the schema or the tool description; breakpointNumber has a schema description referencing breakpoint_set, but the tool description adds little. Coverage is 50% and description does not compensate for the missing sessionId context.

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?

Description clearly states the action (deletes) and the resource (breakpoint) and specifies the method (by number), distinguishing it from set and list tools.

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?

Implies usage when a previously set breakpoint needs to be removed, but does not explicitly contrast with other tools or state prerequisites, though it's evident.

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