Skip to main content
Glama
Arduino Bridge MCP

Arduino Bridge MCP

search_boards

Read-onlyIdempotent

Find installed Arduino board definitions by name or FQBN, even when no board is connected.

Instructions

Find installed board definitions by name or FQBN, even without a board attached.

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": {
      "query": "<query>"
    },
    "name": "search_boards"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYes

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 readOnly, idempotent, non-destructive and open-world, so safety is covered. The description adds that results are limited to *installed* definitions and that no attached board is required — genuinely useful context. It stays silent on matching semantics (substring vs exact, case sensitivity) and result ordering, which is why it is not higher.

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?

One sentence, front-loaded with the verb and resource, with the qualifier at the end. No filler or redundancy.

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?

A one-parameter, low-complexity lookup with an output schema and full annotation coverage — the description needn't explain return values. What it covers (scope, key types, no-hardware condition) is sufficient for correct invocation; only match-behavior detail is missing.

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 burden; it partially does by saying the single query accepts a board name or an FQBN, which is meaningful beyond the bare 'Query' string schema. It does not specify whether matching is partial or exact, or how ambiguity is resolved, leaving the parameter semantics incomplete.

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 ('Find installed board definitions') plus the searchable keys ('by name or FQBN'). This clearly separates it from list_boards and get_board_details in spirit, though no sibling is named 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 clause 'even without a board attached' gives one useful usage condition, implying this is the right tool during discovery/setup when no hardware is connected. It does not say when to prefer this over list_boards (enumerate all) or get_board_details (single known board), so the routing is only implied.

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