Skip to main content
Glama
huaidj-rufus

huaidj-rufus

by huaidj

prepare_native_format

Prepare a USB drive for non-bootable formatting with the original Rufus formatter, including native large-FAT32, while checking filesystem support and device limits; explicit filesystem required.

Instructions

Prepare a whole-USB non-bootable format using the original Rufus formatter, including the native large-FAT32 path. Requires an explicit filesystem. Native availability and actual device limits are checked; no image or synthetic hash is used. Does not erase the 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>",
      "native_options": "<native_options>"
    },
    "name": "prepare_native_format"
  }
}

Input Schema

NameRequiredDescriptionDefault
device_numberYes
native_optionsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/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 reinforces this with 'Does not erase the device', which is exactly the kind of nuance an agent needs for a format tool. It also discloses that native availability and device limits are validated up front, but it does not say what happens on validation failure or how the result is reported.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four short sentences, front-loaded with the core action and capability, then prerequisites and the non-erasure caveat. No filler, though the phrase 'no image or synthetic hash is used' is slightly cryptic without context.

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 0% schema coverage on a nested parameter object, the description should do more. It adequately covers what the tool does, its non-destructive nature, and validation behavior, but leaves the agent guessing about most option fields and about expected results.

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 description coverage is 0% with a nested options object containing six sub-properties, so the description must carry the burden. It only touches the filesystem requirement (and even that is muddied by the 'auto' enum value), leaving device_number, cluster_size, quick_format, volume_label, target_system, and partition_scheme entirely unexplained.

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 names a specific verb and resource ('whole-USB non-bootable format'), names the underlying implementation ('original Rufus formatter'), and flags a distinguishing capability ('native large-FAT32 path'). It also separates itself from image-writing siblings by stating 'no image or synthetic hash is used', though it does not name any sibling tool directly.

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?

It gives a hard prerequisite ('Requires an explicit filesystem') and notes that availability and device limits are checked, which tells the agent something about preconditions. However, there is no explicit guidance on when to pick this over prepare_disk_operation, prepare_usb_write, or dry_run_usb_plan.

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