Skip to main content
Glama
Arduino Bridge MCP

Arduino Bridge MCP

cancel_build

Stops a queued or running Arduino build and frees its toolchain slot so other compilations can proceed.

Instructions

Cancel a queued or running build and release its toolchain slot.

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

Input Schema

NameRequiredDescriptionDefault
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

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, openWorldHint=false, so the mutation/safety profile is partly covered. The description adds useful context beyond them by disclosing the side effect 'release its toolchain slot', which is not in the annotations. However it says nothing about reversibility, whether partial output is discarded, or whether cancelling an already-completed build errors — gaps for a mutation tool.

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?

One front-loaded sentence with the action and its side effect; no filler or redundancy. Its brevity stems from under-specification rather than tight editing, but as written every word earns its place.

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 not be explained, and annotations cover the safety profile. Still, for a state-changing build operation the description omits the single parameter's meaning/source and any error behavior, leaving the definition only minimally sufficient.

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 must carry the burden, and it never mentions build_id at all — not its format, nor where an agent obtains one (e.g., from a compile or status call). The single parameter is largely self-evident from its name and constraints, but the description adds no meaning whatsoever.

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 ('Cancel a queued or running build') and qualifies the scope to queued/running states, which distinguishes it from status-reading siblings in spirit. It does not name any sibling (e.g., get_build_status) explicitly, so differentiation is inferred rather than stated.

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 phrase 'queued or running build' implies the situation in which cancellation makes sense, giving implied usage guidance. There is no explicit when-not guidance (e.g., what happens if the build already finished) and no named alternative for inspecting a build first.

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