Skip to main content
Glama
Sign In
stmctl-mcp

stmctl-mcp

by Sathvik-smarttrak
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

stm32_run_mcu

Start or resume STM32 MCU execution at a specified address or entry point via SWD. Accepts optional hex address for precise control.

Instructions

Start or resume program execution at specified address or entry point.

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

Input Schema

NameRequiredDescriptionDefault
portNoConnection portSWD
addressNoOptional start execution address in hex (e.g. 0x08000000)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.3/5.0
Behavior2/5

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

With no annotations, the description carries the full burden but only says 'start or resume,' which implies the MCU will begin running. It does not disclose whether this halts an existing debug session, whether it requires the device to be connected, or what happens if the address is invalid. This is a minimal disclosure without side-effect information.

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, front-loaded sentence with no fluff. It is efficient and to the point, earning full marks for conciseness.

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?

For a simple two-parameter tool, the description gives the core action but lacks context about preconditions (e.g., a live connection) and post-execution behavior. There is no output schema, and annotations are absent, so this description is minimally viable but not rich.

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?

Schema coverage is 100%, so the description adds little beyond what the schema already provides. The phrase 'address or entry point' aligns with the 'address' parameter but adds no new format or semantic details; the 'port' parameter is also not elaborated.

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 ('start or resume program execution') and the target ('specified address or entry point'). It differentiates from siblings like stm32_reset_mcu by focusing on execution at a custom address 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?

No guidance is provided on when to use this tool versus alternatives like stm32_reset_mcu or after flashing. It does not mention prerequisites (e.g., prior connection) or when 'resume' applies rather than 'start'. The lack of context means an agent must infer usage from the name.

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