Skip to main content
Glama
Arduino Bridge MCP

Arduino Bridge MCP

create_sketch

Destructive

Creates a sketch folder and matching .ino file with default or custom content, letting you save new Arduino sketches in the workspace or sketchbook for editing and compilation.

Instructions

Create a new sketch folder and matching .ino file.

Use location="sketchbook" so the sketch appears in Arduino IDE; the default writes inside the configured workspace.

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>"
    },
    "name": "create_sketch"
  }
}

Input Schema

NameRequiredDescriptionDefault
sketchYes
contentNovoid setup() { } void loop() { }
locationNoworkspace

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.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false and destructiveHint=true, so the agent knows this writes. The description adds that two artifacts are produced (folder plus .ino) and where they land, but it never says what happens if a sketch of that name already exists -- the exact question the destructiveHint raises. That is a meaningful omission for a write operation.

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 sentences, both earning their place, with the verb and resource front-loaded and the location advice immediately after. No filler or restatement of the tool name.

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, so return values need not be described, and the location semantics are well covered for a three-parameter tool. The remaining gap is collision behavior on an existing sketch name, which matters given the destructive hint.

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 coverage is 0%, so the description must carry the load. It explains the non-obvious `location` enum thoroughly, but says nothing about whether `sketch` is a bare name or may contain path segments, nor about the `content` template beyond the default the schema already shows. Partial compensation only.

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?

The description opens with a concrete verb+resource pair: creates a sketch folder and a matching .ino file. That is specific enough that an agent can distinguish it from write_sketch_file or compile_sketch, though it never explicitly contrasts itself with those siblings.

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?

It gives real guidance on choosing between the two `location` values (sketchbook for IDE visibility vs. the workspace default), which is useful decision support. It does not say when to use this tool rather than write_sketch_file for an existing sketch, leaving the primary routing question implied.

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