Skip to main content
Glama

firmware_build

Destructive

Runs installed C51, BL51, and OH51 to build 8051 firmware, preserve logs, and verify Intel HEX output, not simulation.

Instructions

Actually run installed C51, BL51 and OH51; preserve logs and verify Intel HEX. NOT simulation.

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": {
      "project": "<project>"
    },
    "name": "firmware_build"
  }
}

Input Schema

NameRequiredDescriptionDefault
projectYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true and openWorldHint=false, so the risk profile is partly supplied. The description adds that logs are preserved and the Intel HEX is verified, which is genuinely useful behavior detail, but it never explains what is overwritten despite destructiveHint=true (build artifacts? prior output?) or where logs land.

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?

Two short sentences with no filler and the core action front-loaded. The telegraphic 'Actually run installed C51, BL51 and OH51' phrasing is terse to the point of being cryptic about which target it builds.

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

Completeness2/5

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

This is a destructive, no-output-schema build tool with an undocumented required parameter, and the description omits build inputs, output artifact location, log location, and failure behavior. It conveys intent but not enough to invoke correctly without trial and error.

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

Parameters2/5

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

Schema coverage is 0% for the single required 'project' parameter, so the description must compensate and does not. It never says whether 'project' is a path, a project name, or a directory, nor what relative resolution rules apply.

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?

Names the concrete toolchain binaries (C51 compiler, BL51 linker, OH51 converter) and the outcome (run build, verify Intel HEX), which is far more specific than the tool name alone. 'NOT simulation' carves out scope against a firmware_inspect/simulation-style sibling, though it does not name that sibling explicitly.

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?

'Actually run installed C51, BL51 and OH51' implies the prerequisite of an installed toolchain and excludes simulation, which is real guidance. However it never states when to pick this over firmware_inspect or inspection tools, nor what happens when the toolchain is absent.

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