Skip to main content
Glama
Arduino Bridge MCP

Arduino Bridge MCP

compile_sketch

Queues a build of a saved sketch for the specified board FQBN and returns a build ID for polling status.

Instructions

Queue a build of a saved sketch snapshot for this FQBN. Poll get_build_status with the build ID.

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": {
      "sketch": "<sketch>",
      "fqbn": "<fqbn>"
    },
    "name": "compile_sketch"
  }
}

Input Schema

NameRequiredDescriptionDefault
fqbnYes
sketchYes

Output Schema

NameRequiredDescriptionDefault
okYes
dataNo
errorNo
statusYes
warningsNo
request_idNo
next_actionsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations declare readOnly=false, destructive=false, openWorld=false, so the safety profile is already covered. Beyond that, the description adds the key behavioral fact that the call is asynchronous — it queues work and returns a build ID that must be polled — which is not derivable from the annotations or schema.

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 short, front-loaded sentences with no filler. The action comes first and the polling instruction follows naturally.

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?

An output schema exists and carries return-value detail, so the description only needs action, sequencing, and parameter meaning. It handles action and sequencing well; the remaining gap is naming the format/identity of the sketch and FQBN inputs.

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 0%, so the description must compensate. It does hint that 'sketch' is a saved snapshot and 'fqbn' identifies a board, but it never clarifies whether sketch is an ID, name, or path, nor what an FQBN looks like, leaving ambiguity for both required parameters.

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 and resource: 'Queue a build of a saved sketch snapshot' scoped to an FQBN. An agent can tell this is the compile step rather than a write/upload step, though it doesn't explicitly contrast with siblings like upload_sketch that may also trigger compilation.

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?

Gives clear post-invocation guidance ('Poll get_build_status with the build ID'), which is genuinely useful sequencing. However, there is no guidance on when to choose this over other build/upload paths, nor on prerequisites such as the sketch already existing as a saved snapshot.

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