Skip to main content
Glama
Sign In
stm32c0-mcp

stm32c0-mcp

by praderppp
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

flash

Program .elf, .bin, or .hex firmware onto an STM32C011 over SWD via ST-LINK using STM32_Programmer_CLI. Optionally set a serial number to target a specific probe.

Instructions

Flash a .elf/.bin/.hex to an STM32C011 over SWD via ST-LINK using STM32_Programmer_CLI. Set serial_number to target one probe among several.

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": {
      "file_path": "<file_path>"
    },
    "name": "flash"
  }
}

Input Schema

NameRequiredDescriptionDefault
partNoSTM32C011F6Ux
eraseNoall
verifyNo
file_pathYes
reset_modeNorst
frequency_khzNo
serial_numberNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations, the description must carry behavioral transparency on its own. It discloses the underlying tool (STM32_Programmer_CLI) and the flashing mechanism, but does not mention side effects like erasing existing firmware, verification behavior, or failure modes. This is a moderate disclosure.

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?

Two sentences: the first delivers the core functionality, the second adds a practical tip about probe selection. No redundant words.

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 has no annotations and no output schema, so the description must provide complete operational context. It gives the target, interface, and tool, but omits prerequisites, output/return behavior, and how to discover serial numbers (e.g., via list_probes). It is adequate but not rich.

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?

Schema coverage is 0%, so the description is the only source of parameter meaning. It explains serial_number's purpose and the accepted file extensions for file_path, but leaves erase, verify, reset_mode, frequency_khz, and part undocumented. This is insufficient for a 7-parameter tool.

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 specifies the action (Flash), the target (STM32C011), the interface (SWD via ST-LINK), and the accepted file formats (.elf/.bin/.hex), distinguishing it from sibling tools like build and list_probes.

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?

It provides clear context that this tool is for flashing firmware to an STM32C011, and the serial_number tip addresses multi-probe environments. However, it does not explicitly state when to use it over alternatives or when not to use it, so it falls 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