Skip to main content
Glama
Arduino Bridge MCP

Arduino Bridge MCP

upload_sketch

Destructive

Flashes a one-time plan to an Arduino board after local terminal approval and fresh target verification, ensuring only the confirmed build is written.

Instructions

Flash a one-time upload plan after local terminal approval and fresh target verification.

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": {
      "upload_id": "<upload_id>"
    },
    "name": "upload_sketch"
  }
}

Input Schema

NameRequiredDescriptionDefault
upload_idYes

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

B3.1/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and openWorldHint=true, but the description adds real signal beyond them: the operation is one-time (non-idempotent), requires prior local terminal approval, and demands a fresh target verification before firing. What is missing is the consequence of flashing — e.g. that existing firmware on the target is overwritten.

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

Conciseness3/5

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

It is a single well-formed sentence with the action verb front-loaded and no filler. The compactness tips into under-specification, though: "one-time upload plan" and "fresh target verification" are dense jargon that does little to orient a reader.

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?

An output schema exists, so return values need no explanation. But for a destructive, open-world, single-parameter tool that performs a hardware write, the definition omits what gets overwritten, how upload_id is obtained, and what constitutes the required verification, leaving meaningful gaps.

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?

There is one required parameter, upload_id, with 0% schema description coverage, and the description says nothing about it — not its origin, format, or lifetime. The agent must guess that it comes from a preceding prepare call, which is exactly the kind of meaning the description should supply.

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

Purpose3/5

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

"Flash a one-time upload plan" names a verb and an object, but "upload plan" is internal jargon that never resolves into a concrete resource like a compiled sketch or board. An agent cannot distinguish this from prepare_upload or write_sketch_file on the strength of this description alone.

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?

The phrase "after local terminal approval and fresh target verification" implies a prerequisite sequence, so ordering is hinted at. However, it never names the sibling that produces the upload plan or states when to prefer this over prepare_upload, leaving the workflow implicit.

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