Skip to main content
Glama
huaidj-rufus

huaidj-rufus

by huaidj

dry_run_usb_plan

Validates a prepared USB write plan through the native Rufus adapter without writing to the drive. Use it to catch plan issues before a confirmed write; a successful check does not complete the USB.

Instructions

Validate a prepared plan with the native Rufus adapter without writing the USB. May display Windows UAC. A successful dry run is not a completed USB write.

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": {
      "plan_id": "<plan_id>",
      "confirmation": "<confirmation>"
    },
    "name": "dry_run_usb_plan"
  }
}

Input Schema

NameRequiredDescriptionDefault
plan_idYesThe unexpired plan ID returned by prepare_usb_write.
confirmationYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations declare readOnlyHint=false and destructiveHint=false, and the description adds genuinely useful context beyond them: no USB writing occurs, a UAC prompt may appear (elevation exposure), and success does not equal a completed write. It does not disclose whether the plan is consumed, expires, or is re-usable, which matters given idempotentHint=false.

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, each earning its place: capability first, then the elevation caveat, then the success-semantics warning. No filler and nothing buried.

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?

For a two-parameter validation tool with no output schema, the description covers the operation, the side-effect boundary, and the elevation prompt. The notable remaining gap is the undocumented required 'confirmation' parameter, which an agent cannot confidently fill from this definition.

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 only 50%: plan_id carries a good schema description, but the required 'confirmation' parameter is completely undefined in both schema and tool description. The description does not compensate at all, leaving the agent guessing what value to supply for the second required parameter.

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?

The description gives a specific verb (validate), a specific object (a prepared plan) and an explicit scope boundary (without writing the USB), plus the adapter used (native Rufus). An agent can distinguish this from prepare_usb_write or write_usb without opening another schema.

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?

Usage context is implied rather than stated: the description says it validates a 'prepared' plan and notes a successful dry run is not a completed write, which hints at placement before the real write. It never explicitly says when to call this versus write_usb or verify_usb_image, nor whether it is a prerequisite.

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