mcp-micropython-bridge

Overview Schema Source Related Servers Discussions Admin

micropython_interrupt

Send Ctrl-C to a MicroPython device to stop the currently running script or command, halting execution for debugging or recovery.

Instructions

Ctrl-C を送って実行中の処理を中断

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": "micropython_interrupt"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`ok`	Yes
`error`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 13, 2026

TDQS

B3.4/5.0

Behavior3/5

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

No annotations are provided, so the description carries the full burden. It discloses the mechanism (sending Ctrl-C) and the expected effect (interrupting processing), which is useful behavioral context. However, it doesn't state whether the interruption is graceful, whether state is preserved, what happens if no process is running, or what the output contains. Some behavioral transparency is present but significant gaps remain.

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?

A single, compact sentence that is front-loaded with the core action. No unnecessary words or structure.

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?

The tool is simple (no parameters, output schema exists), so the description doesn't need to explain return values. However, for an interrupt operation with no annotations, more context about behavior (e.g., what gets interrupted, whether it's safe, effects on connection state) would help an agent use it correctly. The description is adequate but leaves notable gaps.

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?

The tool takes zero parameters, so parameter semantics are not applicable. Baseline 4 is appropriate for a parameterless tool.

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 action (send Ctrl-C) and its effect (interrupt running processing). An agent can distinguish this from siblings like micropython_reset or micropython_disconnect, though the description could more explicitly differentiate from reset (soft interrupt vs hard reset).

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?

No guidance on when to use this tool versus alternatives like micropython_reset or micropython_disconnect. The description implies it stops a running process but doesn't say when this is preferable to a full reset. No exclusions or prerequisites are provided.

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