Skip to main content
Glama
huaidj-rufus

huaidj-rufus

by huaidj

verify_usb_image

Read-onlyIdempotent

Verifies a USB's physical image-length prefix and compares its SHA-256 hash to a locked source image, with no disk writes.

Instructions

Read back the exact physical image-length prefix from an identified USB and compare SHA-256 to the locked source image. No disk writes. Windows may request administrator approval. Returns a job to poll.

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

Input Schema

NameRequiredDescriptionDefault
imageYesConfigured image alias or local .iso/.img path within configured image roots.
device_numberYes
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

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds useful context beyond annotations: it notes that Windows may request administrator approval and that the tool returns a job to poll, clarifying the async execution model.

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?

The description is four tight sentences, front-loaded with the core action and followed by operational notes about disk writes, admin approval, and job polling. Every sentence adds distinct information without redundancy.

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 description covers the essential behavior: read-only verification, SHA-256 comparison, no disk writes, possible admin escalation, and async job return. It could go further by explaining what the polled job result contains or which sibling polls it, especially since there is no output schema.

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?

The schema description coverage is 67%, with image and expected_sha256 documented but device_number left without a schema description. The description adds some meaning via 'identified USB' and 'locked source image', but it does not clarify device_number semantics or the physical image-length prefix concept.

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 states a specific verb (read back and compare SHA-256), a specific resource (USB image), and the exact scope (physical image-length prefix). It distinguishes itself from write-oriented siblings such as write_usb and prepare_usb_write by explicitly framing the operation as verification.

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 use case is clear from context—verifying a USB against an expected hash—but the description does not explicitly say when to use this tool versus alternatives like inspect_disk_image or dry_run_usb_plan. No when-not-to-use guidance or named alternatives are provided.

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