Skip to main content
Glama
Arduino Bridge MCP

Arduino Bridge MCP

get_cli_version

Read-onlyIdempotent

Detect the installed Arduino CLI and return its version, discovery source, and read-only capabilities so agents can verify the available command-line environment.

Instructions

Detect Arduino CLI and return its version, discovery source, and read-only capabilities.

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": "get_cli_version"
  }
}

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

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered structurally. The description adds genuine but modest value by signaling that a 'discovery source' is reported and that capabilities surfaced are read-only, hinting at fallback detection paths. It does not state what happens when no CLI installation is found, which is the primary behavioral question for a detection tool.

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?

A single telegraphic sentence with no filler, and the identifying noun ('Arduino CLI') is front-loaded right after the verb. Nothing could be removed without losing information.

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?

An output schema exists, so return values need no explanation, and the tool is a simple, parameter-light read. The definition is therefore close to complete, with the only real shortfall being the undocumented include_paths flag relative to a 0%-covered schema.

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?

Schema description coverage is 0% and the single parameter 'include_paths' (default false) is never mentioned in the description, so its meaning and effect are documented nowhere. The description's enumeration of return fields does not compensate for this gap in the input contract.

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?

The description uses a specific verb ('Detect') paired with a specific resource ('Arduino CLI') and enumerates what it returns: version, discovery source, and read-only capabilities. That makes its purpose unmistakable and clearly distinct from the board/sketch/build siblings, though it never explicitly names a sibling to contrast with.

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: an agent can infer this is a pre-flight/environment check because it 'detects' the CLI and reports version and capabilities. There is no explicit statement of when to call it (e.g. before compiling or installing), no when-not guidance, and no reference to the related get_environment sibling.

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