Skip to main content
Glama
Arduino Bridge MCP

Arduino Bridge MCP

install_package

Destructive

Installs an indexed Arduino core or library at an explicit version for board builds, with server-owner opt-in required.

Instructions

Install an indexed core or library at an explicit version. 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": {
      "kind": "<kind>",
      "name": "<name>",
      "version": "<version>"
    },
    "name": "install_package"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindYes
nameYes
versionYes

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.3/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, so the agent knows this is a mutating, externally-reaching operation. The description adds a genuine permission prerequisite ('server-owner opt-in') beyond the annotations, but says nothing about side effects such as overwriting an existing version or impact on builds.

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 short sentences, zero filler, with the core action front-loaded and the prerequisite appended. Nothing is redundant or vague.

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, which lowers the burden. Still, for a destructive, open-world install operation the description omits what happens to an already-installed version and how to satisfy the opt-in prerequisite.

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?

With 0% schema description coverage across three required parameters, the description must carry the semantics. It contributes two real constraints — 'indexed' (name must match a known core/library) and 'explicit version' (no ranges or 'latest') — but leaves name format, where indexed names come from, and version string conventions unspecified.

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 ('Install an indexed core or library') plus the version constraint. The verb/resource pair inherently separates it from siblings like list_cores, search_libraries, or compile_sketch, 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 prerequisite 'Requires server-owner opt-in' gives real when-to-use context, which is valuable. However, there is no guidance on what to do if opt-in is absent, no pointer to how to discover installable names (e.g., via list/search tools), and no when-not-to-use conditions.

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