flashgate

Overview Schema Source Related Servers Discussions Admin

build

Idempotent

Compile board firmware incrementally, recompiling only changed files without touching hardware. Use for a quick failure loop; verify runs the same compilation internally.

Instructions

Compile the board's firmware (incremental — recompiles only what changed). No hardware is touched.

Mostly useful on its own for a fast failure loop; verify runs the
same build internally, so you don't need this before verify. Result:
succeeded + exit_code 0 = clean build; failed + BUILD_FAILED = the
compiler output in data.log names the offending file and line. The
binary lands at the profile's artifact path, ready for flash.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`board`	No	Path to the board profile YAML (e.g. boards/apollo-h743.yaml). Omit to use the server's --board argument, else the default search path.

Output Schema

TableJSON Schema

Name	Required	Default
`code`	Yes
`data`	No
`policy`	No
`status`	Yes
`summary`	Yes
`evidence`	No
`warnings`	No
`exit_code`	No
`schema_version`	No	1.0

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 13, 2026

TDQS

A4.7/5.0

Behavior5/5

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

With only idempotentHint available, the description carries the behavioral load fully: it discloses incrementality, that no hardware I/O occurs, the two result shapes (succeeded/exit_code 0 vs failed/BUILD_FAILED), where diagnostics surface (data.log naming file and line), and where the artifact lands. These are traits the annotations do not cover.

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?

Front-loads the operation and its incremental/non-hardware nature, then moves to routing and outcome semantics. Every sentence is functional — the result-code and artifact-path sentences directly support post-call interpretation.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite an output schema existing, the description adds interpretive value (log file naming the offending line, artifact path readiness for flash) rather than repeating return structure, and the parameter gap is covered by the schema. Nothing needed to call or interpret this tool is missing.

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 description coverage is 100% and the single 'board' parameter is fully documented with default and fallback behavior, so the schema does the work. The description adds no parameter-level detail beyond what is already structured, which is the expected baseline.

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?

States a specific verb and resource ('Compile the board's firmware') and immediately scopes it with 'incremental — recompiles only what changed' and 'No hardware is touched', which cleanly separates it from flash and probe. An agent can identify the operation without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly frames when to use it ('a fast failure loop') and when it is unnecessary ('verify runs the same build internally, so you don't need this before verify'), naming the sibling that subsumes it. This is precisely the kind of routing guidance that prevents redundant calls.

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

Deploy Server