Skip to main content
Glama
Arduino Bridge MCP

Arduino Bridge MCP

get_environment

Read-onlyIdempotent

Check Arduino IDE and CLI availability plus effective CLI configuration, optionally including paths, to verify the build environment before compiling or uploading sketches.

Instructions

Check Arduino IDE, CLI, and effective CLI configuration. Request paths only when needed.

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_environment"
  }
}

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 closed-world scope, so the safety profile is fully covered without the description. The description adds only that the result aggregates three configuration sources plus the notion that paths are costly to fetch; it says nothing about permissions, failure modes, or latency.

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 sentences with the scope statement front-loaded and the parameter caveat second. Nothing is padded, though the first sentence could have used a sharper verb than 'Check'.

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?

For a one-optional-boolean diagnostic tool with full annotations and an output schema, the description covers what is inspected and how to treat the optional parameter. The only gap is that 'effective CLI configuration' is never unpacked, but the output schema carries the return detail.

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 description coverage is 0% for include_paths, so the description must compensate, and it does: 'Request paths only when needed' signals that the boolean triggers extra filesystem path data and should be used sparingly. That is meaningful guidance beyond the bare boolean and its false default.

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

Purpose3/5

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

The description names the resource set it inspects (Arduino IDE, CLI, and effective CLI configuration), so the agent knows this is an environment/diagnostics read. However, the verb 'Check' is vague and it never distinguishes itself from close siblings like get_cli_version, leaving overlap unresolved.

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?

'Request paths only when needed' is real conditional guidance, but it only governs the parameter, not when to call this tool versus get_cli_version or the list_* tools. Usage is implied (environment inspection) rather than stated, with no exclusions.

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