Skip to main content
Glama
Arduino Bridge MCP

Arduino Bridge MCP

list_sketches

Read-onlyIdempotent

Lists sketches in the Arduino sketchbook, matching the set shown in Arduino IDE, and optionally includes their file paths for quick selection.

Instructions

List sketches in the Arduino sketchbook, the same set Arduino IDE shows.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_sketches"
  }
}

Input Schema

NameRequiredDescriptionDefault
include_pathsNo

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

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world behavior, so the safety profile is fully covered. The description's only extra contribution is equating the result with the IDE's sketchbook view, which does not explain ordering, pagination, or what include_paths changes.

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?

A single front-loaded sentence with no filler, which is appropriately sized for a simple list operation. It is terse to the point of omitting the one parameter, but no wording is wasted.

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 not be described, and annotations carry the safety profile. However, for a tool whose only knob is undocumented in both schema and description, the definition falls short of complete.

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 parameter, include_paths, with 0% schema description coverage, and the description never mentions it. The agent cannot tell from either source what paths would be included or what the output looks like when toggled, so this leaves a real gap.

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 ('List sketches in the Arduino sketchbook') and clarifies scope with 'the same set Arduino IDE shows.' This distinguishes it implicitly from the singular get_sketch and from the other list_* tools, though it never names an alternative 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?

The Arduino IDE framing implies when the tool is relevant (enumerating the user's visible sketchbook), but there is no explicit when-to-use, when-not-to-use, or pointer to get_sketch for single-sketch lookup. Usage must be inferred.

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