Skip to main content
Glama
huaidj-rufus

huaidj-rufus

by huaidj

usb_write_status

Read-onlyIdempotent

Check the status and progress of a USB write or dry-run job, distinguishing launch, native completion, failure, and cases needing attention.

Instructions

Read the native result and progress of a USB write or dry-run job. Distinguishes process launch, native reported completion, failure, and required attention.

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": {
      "job_id": "<job_id>"
    },
    "name": "usb_write_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
job_idYes

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 already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the bar is lower; the description still adds real value by enumerating the state taxonomy it reports: process launch, native reported completion, failure, and required attention. That distinction between 'process launched' and 'natively reported complete' is the kind of nuance the annotations cannot convey, though return shape and progress representation remain unspecified.

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?

Two tight sentences, front-loaded with the action and resource, with no filler. 'Required attention' is slightly vague as a terminal state but the sentence still earns its place by naming the outcome categories.

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, the description carries the burden of describing return values, and it covers this only partially: it names that progress and a native result exist and lists outcome states, but says nothing about the fields, progress units, or error detail. It is adequate to select and call the tool, but thin for interpreting the response.

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?

There is one required parameter (job_id) at 0% schema description coverage, and the description never mentions it, let alone its UUID format or where a job_id comes from (presumably a prior prepare/write call). With low coverage the description was expected to compensate and does not.

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?

States a specific verb ('Read') and a specific resource ('native result and progress of a USB write or dry-run job'), plus the state set it distinguishes. It does not differentiate itself from status-oriented siblings such as disk_job_status or rufus_status, so an agent must infer which status tool applies to which job type.

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 (polling a USB write or dry-run job) is implied by 'Read the native result and progress' and 'dry-run job', but there is no explicit when-to-use, no when-not, and no mention of polling cadence or which sibling covers other job kinds. Usage is inferable rather than stated.

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