Skip to main content
Glama

flipper_badusb_run

Destructive

Launch the Bad USB app and run a saved DuckyScript from /ext/badusb/ against the connected host; use only on PCs you own or are authorized to test.

Instructions

Launch the Bad USB app with a saved DuckyScript from /ext/badusb/. The script runs against whatever host the Flipper's USB is plugged into — use only on a PC you own or are authorised to test.

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": {
      "filename": "<filename>"
    },
    "name": "flipper_badusb_run"
  }
}

Input Schema

NameRequiredDescriptionDefault
filenameYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare destructiveHint, openWorldHint, and non-idempotency, but the description adds real context beyond them: the payload executes on the connected USB host, the script must already exist in /ext/badusb/, and there is an authorization boundary. It does not describe failure behavior (e.g., missing file) or whether execution blocks.

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 tight sentences with zero filler. The action and location constraint are front-loaded, and the safety warning follows naturally.

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?

The tool has an output schema, so return values need not be explained. The description covers source directory, execution target, and safety. Minor gaps remain around error handling for a nonexistent script and whether the app must be installed, but the essential information an agent needs is present.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0% for the single 'filename' parameter, so the description must compensate. It usefully states the file is a saved DuckyScript located in /ext/badusb/, which constrains the value, but it does not clarify whether an extension is expected or how paths are resolved.

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?

The description gives a specific verb ('Launch') and resource ('Bad USB app with a saved DuckyScript'), plus the directory the script must come from (/ext/badusb/). It implicitly distinguishes this from sibling creation tools like flipper_badusb_create, though it does not name any sibling explicitly.

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?

It provides a clear cautionary context: the script runs against whatever host the Flipper's USB is plugged into, and should only be used on a PC you own or are authorised to test. That is an explicit when-not-to-use constraint, though it does not point to alternative tools for other scenarios.

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