Skip to main content
Glama
Sign In
Arduino MCP Server

Arduino MCP Server

by niradler
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Search Arduino Packages

search
Read-only

Search for Arduino cores or libraries with specific terms to narrow results and get the latest version details for libraries.

Instructions

Search for Arduino cores or libraries.

Note: Library searches return only latest version details to reduce output size. Use more specific search terms to narrow results (e.g., "Adafruit_SSD1306" instead of "display").

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>",
      "package_type": "<package_type>"
    },
    "name": "search"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYes
package_typeYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.3

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already indicate readOnlyHint and openWorldHint. The description adds value by noting the limitation on library version data and the advice on narrowing results. No contradictions with annotations.

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 concise sentences with front-loaded key information. No redundant or unnecessary content. Efficient and clear.

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?

Given the presence of output schema and annotations, the description adequately covers the main behaviors and limitations. Could mention pagination or error handling but acceptable for a search tool.

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 has 0% description coverage, so description must compensate. It implies package_type relates to 'cores or libraries' but does not explicitly define valid values or explain query. Insufficient guidance beyond the tool's purpose.

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?

Description clearly states it searches for Arduino cores or libraries, which is a specific verb and resource. While it distinguishes from siblings like install_core or list_installed_libraries, it does not explicitly differentiate from any potential other search tools, but none exist in sibling list.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides explicit guidance that library searches return only latest version details and advises using specific search terms. However, it does not mention when not to use this tool or suggest alternatives.

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

Deploy Server

Other Tools