Skip to main content
Glama

cubemx1_ioc_build

Compiles target JSON offline into a canonical .ioc file that CubeMX loads directly, validating unsupported or malformed fields and reporting conflicts instead of ignoring them.

Instructions

Compile a target JSON offline into a canonical .ioc that CubeMX loads directly. Does not start CubeMX and runs no command sequence. The target describes: device, pins and signals, peripheral modes and parameters, clock target frequencies or explicit RCC parameters, interrupts, DMA, middleware, RTOS scalar parameters, project name / output directory / toolchain. Unsupported or malformed fields are reported as unsupported/unknown/conflict and are never silently ignored.

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": {
      "target": "<target>"
    },
    "name": "cubemx1_ioc_build"
  }
}

Input Schema

NameRequiredDescriptionDefault
outputNoOutput .ioc path; defaults to project.output_dir/<project.name>.ioc from the target
targetYesTarget: a JSON object, or JSON text, or a .json file path. The top level must carry contract: cubemx1.ioc/1 or cubemx1.ioc/2

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations supplied, the description carries the burden well: it discloses that nothing is executed, that no process is launched, and that unsupported/unknown/conflict fields are surfaced rather than silently dropped. It omits what happens when the output path already exists (overwrite? error?) and what is returned on success, which are the remaining behavioral gaps for a file-writing tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core action and its distinguishing constraint are front-loaded in the first two sentences; the field enumeration follows as supporting detail. The list of target contents is long but each item maps to real input domain, so it is dense rather than padded.

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?

No output schema exists, so the description should say what comes back (the written .ioc path, diagnostics, or nothing), and it does not. Input-side coverage is strong, but an agent cannot tell from this text whether success yields an artifact path or just a status.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3; the description earns above that by enumerating what a valid target actually contains (device, pins/signals, peripheral modes, clock frequencies, interrupts, DMA, middleware, RTOS scalars, project settings) and by restating the required contract version. That is genuine meaning the schema's one-line 'JSON object, text, or file path' does not convey.

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 opens with a specific verb and resource: compile a target JSON offline into a canonical .ioc. The clause 'Does not start CubeMX and runs no command sequence' explicitly separates it from the generation sibling, so an agent can distinguish the two without reading either schema.

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?

The 'offline' framing plus the explicit negatives ('does not start CubeMX', 'runs no command sequence') give a clear condition for choosing this tool over a live-generation sibling. It stops short of naming that sibling as the alternative, so the when-not is implied rather than stated.

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