Skip to main content
Glama

cubemx1_ioc_import

Import an STM32CubeMX .ioc file into target JSON, mapping known objects to advanced fields and reporting unknown keys under extensions.ioc without starting CubeMX.

Instructions

Import a .ioc into an advanced target JSON (cubemx1.ioc/2): understood objects go into advanced fields, unknown keys go into extensions.ioc and are reported one by one. Does not start CubeMX.

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": {
      "ioc": "<ioc>"
    },
    "name": "cubemx1_ioc_import"
  }
}

Input Schema

NameRequiredDescriptionDefault
iocYespath of the .ioc to import
outputNowhich JSON to write; defaults to the .json with the same name

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

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 does useful work: it explains the mapping behavior (known objects to advanced fields, unknown keys to extensions.ioc and reported individually) and clarifies that CubeMX is not launched, so no external side effects occur. It does not say whether an existing output file is overwritten, what the reporting looks like, or how failures are surfaced.

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 tight sentences: the core behavior and the fallback handling of unknown keys come first, and the 'does not start CubeMX' caveat closes it. Nothing is redundant or padded.

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?

For a two-parameter conversion tool with no output schema, the description adequately covers the shape of what is produced and how unrecognized keys are handled. Minor gaps remain around overwrite semantics and error/report format, but nothing that would prevent a correct invocation.

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 both 'ioc' and 'output' (including the default output path behavior) are already documented in the schema. The description adds no further meaning about path formats or relative-path resolution, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (import), resource (.ioc file), and concrete target (advanced target JSON, cubemx1.ioc/2), so the transformation is unambiguous. It does not explicitly contrast with siblings such as cubemx1_ioc_generate or cubemx1_ioc_check, but the verb and format make it distinguishable.

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?

Usage is implied by the conversion described: use this to turn an .ioc into the advanced JSON representation. The only explicit boundary is 'Does not start CubeMX', which rules out one expectation, but there is no guidance on when to prefer this over the sibling generate/build/check tools or what prerequisites exist.

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