Skip to main content
Glama
huaidj-rufus

huaidj-rufus

by huaidj

list_usb_devices

Read-onlyIdempotent

Identify USB-eligible physical disks with model, capacity, drive letters, and stable identity while excluding internal and active system disks from writable use.

Instructions

List physical disks with USB eligibility, model, capacity, mounted letters, and an opaque stable identity. Internal and active system disks are never writable through this bridge.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

The annotations already establish this as a read-only, idempotent, non-destructive closed-world operation. The description adds useful context by naming returned fields and clarifying that internal and active system disks are never writable through this bridge, though it does not describe ordering or return structure.

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?

Two compact sentences, front-loaded with the listing purpose and followed by a relevant safety constraint. No filler or 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?

For a simple zero-parameter read-only listing tool with annotations but no output schema, the description is largely complete: it names the key returned fields and states an important safety boundary. Minor gaps remain around ordering, whether internal disks are included in output, and exact result structure.

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 tool takes no parameters, so there is no parameter semantics to document. Baseline 4 applies because no input explanation is needed.

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 and resource: list physical disks with USB eligibility-related fields. It is clear what the tool does, but it does not explicitly differentiate itself from nearby sibling tools such as disk_details or disk_capabilities.

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 'USB eligibility' framing implies the tool is used to enumerate candidate USB disks, but there is no explicit when-to-use guidance, no mention of alternatives, and no stated exclusions beyond the safety note about internal and active system disks.

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