Skip to main content
Glama
Arduino Bridge MCP

Arduino Bridge MCP

get_board_details

Read-onlyIdempotent

Retrieve configuration options for an installed Arduino board by FQBN to inspect supported settings before compiling or uploading.

Instructions

Get board configuration options for an installed FQBN.

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

Input Schema

NameRequiredDescriptionDefault
fqbnYes

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.4/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 open-world behavior, so the safety profile is covered. The description adds only the precondition that the FQBN must be for an installed board; it says nothing about whether unknown FQBNs error, what 'configuration options' contains, or how large the response is.

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?

One short sentence with no filler, and the resource is front-loaded ahead of the scoping qualifier. It is efficient, though so terse that it borders on under-specification.

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 cover the safety profile. Still, for a lookup tool whose only parameter is undocumented in the schema, the description could say more about the FQBN format and behavior on unknown or not-installed boards.

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% for the single fqbn parameter, so the description carries some burden. It does clarify that fqbn identifies an installed board, which is genuine added meaning, but it does not explain the FQBN format or where to obtain one.

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+resource: get board configuration options, scoped to an installed FQBN. That is clearly distinct from siblings like list_boards or search_boards, though the description never names those alternatives to reinforce the distinction.

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?

Usage is only implied: the phrase 'for an installed FQBN' hints that the board must already be installed (i.e., discoverable via list_boards/search_boards first), but there is no explicit when-to-use, when-not-to-use, or named alternative.

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