Skip to main content
Glama
Arduino Bridge MCP

Arduino Bridge MCP

prepare_upload

Creates a five-minute approval plan for uploading a specified build to a serial port and shows the approval file to the user.

Instructions

Create a five-minute plan for one successful build and serial port. Show approval_file to the user.

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": {
      "build_id": "<build_id>",
      "port": "<port>"
    },
    "name": "prepare_upload"
  }
}

Input Schema

NameRequiredDescriptionDefault
portYes
build_idYes

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

C2.7/5.0
Behavior3/5

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

The annotations establish that this is not read-only and not destructive, but the description adds useful behavioral context: it produces an approval_file that must be surfaced to the user, implying a review or approval step. However, it does not clarify whether any state is created, what the five-minute plan contains, what happens after approval, or how failures are handled.

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?

The description is two short sentences with no obvious filler, and the key output behavior is placed second. It is compact, though the phrase 'five-minute plan' is somewhat cryptic rather than explanatory.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Although an output schema exists and return values need not be explained, the tool has two required parameters with no schema descriptions and an ambiguous role in the upload workflow. The description should at minimum clarify that it prepares rather than performs an upload, when to call it, and where the build_id and port values come from.

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%, so the description carries the full burden for explaining build_id and port. It only indirectly maps them to 'build' and 'serial port' without describing formats, valid sources, or examples, leaving both required parameters substantively undocumented.

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 says it creates a 'five-minute plan for one successful build and serial port,' which implies preparing for an upload but never states that explicitly. It does not distinguish the tool from the sibling upload_sketch or explain what the plan actually consists of.

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

Usage Guidelines2/5

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

There is no guidance on when to call this tool, what must happen before it, or how it relates to upload_sketch or compile_sketch. The only directive is to show an approval_file to the user, which is an output-handling instruction rather than usage guidance.

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