Load CubeMX configuration from an existing .ioc file and generate STM32 project code. Regenerate firmware after pin or peripheral changes to keep your code in sync.
Runs CubeMX config load + project generate on an existing .ioc.
| Name | Required | Description | Default |
|---|---|---|---|
| projectPath | Yes | Path to project directory or .ioc file |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It states 'generate' which implies file writing, but does not disclose potential overwriting or other side effects. It is neither fully transparent nor misleading.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, concise sentence with no redundancy or irrelevant content. It is well-structured and front-loads the core action.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple tool with one parameter and no output schema, the description is complete enough. It specifies the prerequisite (existing .ioc) and the action, though it does not explain post-generation behavior. This is acceptable given the simplicity.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema provides a description for the sole parameter, projectPath, indicating it can be a directory or .ioc file. Since schema coverage is 100%, the baseline is 3; the tool description adds no extra semantic beyond the schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool's function: loading CubeMX config and generating the project. It specifies the target (an existing .ioc file) and distinguishes it from siblings like creating a new project or configuring pins.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies when to use the tool (when an existing .ioc file is present) and differentiates from creation tools. It does not explicitly mention alternatives, but the context of sibling tools and the direct wording make the usage clear enough.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.