Skip to main content
Glama
huaidj-rufus

huaidj-rufus

by huaidj

prepare_usb_write

Creates an expiring USB write plan tied to a physical device and verified image hash, showing the destructive effect and required confirmation without erasing or formatting.

Instructions

Prepare an expiring USB write plan bound to the physical device identity and verified image hash. Returns the exact destructive effect and required confirmation. Does not erase or format a device.

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": {
      "device_number": "<device_number>",
      "image": "<image>",
      "expected_sha256": "<expected_sha256>"
    },
    "name": "prepare_usb_write"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeNodd
imageYesConfigured image alias or local .iso/.img path within configured image roots.
device_numberYes
native_optionsNo
expected_sha256YesExpected SHA-256 obtained from a trusted publisher or an explicitly selected local image.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior4/5

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

Beyond the annotations (readOnly=false, destructive=false, idempotent=false), the description contributes real behavior: the plan expires, it is bound to device identity and a verified hash, and it surfaces the exact destructive effect plus the required confirmation. The non-idempotent trait is only obliquely implied by "expiring" and the plan's lifetime is never specified.

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?

Three short sentences with no filler, front-loading the action and then the safety boundary. Every sentence carries distinct information.

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?

With no output schema and a nested native_options object, the description does partially compensate by saying the return includes the destructive effect and the confirmation requirement. It is still incomplete: it does not say whether a plan identifier is returned to hand to write_usb, how long the plan lives, or how mode and native_options change what gets reported.

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 coverage is 40%, and the description only gestures at device_number ("physical device identity") and expected_sha256 ("verified image hash") without adding meaning beyond the schema's own text. The mode enum (dd vs iso) and the entire native_options object (filesystem, partition_scheme, quick_format, volume_label) are never mentioned, even though they directly shape the destructive effect the plan reports.

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 uses a specific verb and resource ("Prepare an expiring USB write plan") and scopes it to a physical device plus verified image hash, which is clearly distinct from execution-oriented siblings like write_usb. It does not name any sibling to sharpen the boundary, so it stops short of a 5.

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 "Does not erase or format a device" implicitly tells the agent this is a prerequisite step rather than the write itself, which is useful. However, there is no explicit statement of when to call this versus dry_run_usb_plan, prepare_native_format, or prepare_disk_operation, and no mention of what must happen next.

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