mcp-micropython-bridge

Overview Schema Source Related Servers Discussions Admin

micropython_reset_and_capture

Resets a MicroPython device and captures its startup serial output for a set duration, with optional idle timeout and byte limit.

Instructions

デバイスをリセットし、起動直後の出力を一定時間読み取る

Args: capture_duration: リセット後の読み取り最大秒数 idle_timeout: この秒数だけ無通信なら早期終了 max_bytes: 読み取る最大バイト数。超えると truncated=True

Returns: ok: リセットと読み取り呼び出しに成功したら True stdout: 起動後に取得したテキスト reset_ok: リセット操作自体が成功したら True truncated: max_bytes で打ち切られたら True error: エラー時のメッセージ

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": {
      "capture_duration": "<capture_duration>"
    },
    "name": "micropython_reset_and_capture"
  }
}

Input Schema

Name	Required	Description	Default
`max_bytes`	No
`idle_timeout`	No
`capture_duration`	Yes

Output Schema

Name	Required	Description	Default
`ok`	Yes
`error`	Yes
`stdout`	Yes
`reset_ok`	Yes
`truncated`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 13, 2026

TDQS

A4/5.0

Behavior3/5

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

No annotations provided, so the description carries the load. It discloses the truncation behavior, early termination on idle, and separate ok/reset_ok/error fields, which is useful behavioral context. However, it doesn't note side effects of the reset (e.g. state loss on the device) or whether reconnection is needed.

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?

Front-loaded one-line summary followed by concise parameter and return documentation. No filler; every line carries 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-value documentation isn't strictly needed, yet the description provides it directly. Combined with full parameter semantics, the definition is nearly self-sufficient; missing only explicit usage guidance vs siblings.

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 coverage is 0%, so the description must compensate. It defines all three parameters meaningfully: capture_duration as max read seconds, idle_timeout as early-exit threshold, and max_bytes with its truncation consequence. Minor gap: no defaults specified for the optional params.

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

Purpose5/5

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

States a specific compound verb and resource: resets the device AND reads startup output for a duration. Clearly distinguishable from siblings like micropython_reset (reset only) and micropython_read_stream (read only).

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 purpose implies when to use it (capture boot output), but no explicit when/when-not guidance or alternative routing to micropython_reset + read_stream is given, despite many relevant siblings existing.

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