Skip to main content
Glama
huaidj-rufus

huaidj-rufus

by huaidj

rufus_status

Read-onlyIdempotent

Reports bridge version, native-engine availability, supported modes, and image aliases to verify USB preparation capabilities before planning disk operations.

Instructions

Report bridge version, native-engine availability, supported modes, and image aliases.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "rufus_status"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds the content of the report (version, engine availability, modes, aliases), which is useful since no output schema exists, but it doesn't clarify whether 'native-engine availability' is a passive lookup or an active probe that can fail, or what 'bridge' and 'aliases' refer to.

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?

A single dense sentence front-loaded with the verb and the four reported items, with no filler or repetition. Every clause carries information.

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 zero-parameter, read-only tool with no output schema, the definition does the minimum by enumerating the reported fields in place of a return schema. However, the enumerated terms are bridge-specific jargon and there is no guidance on interpretation or on how this status differs from sibling capability/discovery tools.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema declares zero parameters, so there is no per-parameter meaning to add and the baseline for a parameterless tool is 4. Nothing in the description misrepresents the (empty) argument surface.

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 opens with a specific verb+resource pairing ('Report bridge version, native-engine availability, supported modes, and image aliases') so the agent knows this is a read-only status/introspection tool. It does not distinguish itself from plausible siblings such as disk_capabilities or detect_dj_equipment, so it stops short of a 5.

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 only implied by the term 'Report' — an agent can infer this is a pre-flight/environment check, but the description never says when to call it instead of disk_capabilities or detect_dj_equipment, nor any prerequisites. No explicit when-not guidance.

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