Skip to main content
Glama
Arduino Bridge MCP

Arduino Bridge MCP

configure_board_manager

Destructive

Add a third-party Boards Manager index URL so vendor cores like ESP8266 and ESP32 can be searched and installed. Required before non-Arduino cores appear in search.

Instructions

Add a third-party Boards Manager index URL so vendor cores can be searched and installed.

Required before ESP8266, ESP32, and most non-Arduino cores appear in search_cores. Requires server-owner opt-in.

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": {
      "url": "<url>"
    },
    "name": "configure_board_manager"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYes

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

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=true, and openWorldHint=true, and the description usefully adds the server-owner opt-in prerequisite plus the fact that the URL is third-party/external. However, the description never explains why the operation is marked destructive (does it replace or invalidate existing index entries?) nor whether the change persists or requires a restart, which is the main behavioral gap for an opt-in mutation.

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 purposeful sentences plus a one-line prerequisite, with the action front-loaded ahead of the consequence and the constraint. The terse fragment "Requires server-owner opt-in." is efficient rather than wasteful; nothing is padded.

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, and the prerequisite and motivation are covered. For a destructive, open-world configuration mutation it is still thin on consequences: effect on existing index configuration, failure behavior for an invalid URL, and whether a restart or re-index is needed are all unstated.

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

Parameters4/5

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

Schema coverage is 0% for the single `url` parameter, so the description must compensate: it specifies that the value is a Boards Manager index URL for third-party vendor cores, which is meaningful beyond the bare string type and 512-char limit. It does not state the expected format (e.g., package index JSON) or whether multiple URLs can accumulate, keeping it below a 5.

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

Purpose5/5

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

States a specific verb and resource ("Add a third-party Boards Manager index URL") and immediately names the downstream effect on search_cores. This lets an agent distinguish it from search_cores, install_package, and list_cores without inspecting any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives a concrete when-to-use trigger: this must run before ESP8266, ESP32, and most non-Arduino cores become visible in search_cores, and it names the prerequisite of server-owner opt-in. It stops short of explicit when-not guidance or naming whether existing indexes are replaced, so it falls just short of full routing guidance.

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