Skip to main content
Glama
huaidj-rufus

huaidj-rufus

by huaidj

disk_job_status

Read-onlyIdempotent

Reads progress and results of format, image write, or read-back verification jobs, showing native success separately from source/readback hash equality.

Instructions

Read the result/progress of a format, image write or read-back verification job. Native success is distinct from source/readback hash equality.

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

Input Schema

NameRequiredDescriptionDefault
job_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

The annotations already cover the safety profile (readOnly, idempotent, non-destructive), so the description's added value is the note that native success is distinct from source/readback hash equality — a genuinely useful semantic caveat. However, with no output schema, it does not describe the states or fields the caller will receive, leaving a real gap for a status tool.

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 short sentences with the verb and resource front-loaded and no wasted wording. The second sentence is slightly cryptic but earns its place by flagging the success-vs-hash distinction.

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?

For a simple read-only status tool with one parameter, most of the essential context is present. But with no output schema and no described response states, the definition leaves the agent guessing about what a status payload contains and how to interpret 'progress' versus 'result'.

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 exactly one parameter (job_id) with 0% schema description coverage, so the description must carry the burden. It never mentions job_id, how to obtain it, or whether it identifies a job from a prior prepare/execute call; only the word 'job' indirectly implies this.

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 resource ('result/progress') scoped to three job types: format, image write, and read-back verification. The purpose is unambiguous, though it does not distinguish itself from sibling status tools such as rufus_status or usb_write_status.

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 is implied rather than stated: an agent can infer this is the polling tool for jobs created by the prepare/execute operations. There is no explicit when-to-use guidance, no mention of polling cadence, and no routing away from the other *_status siblings.

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