Skip to main content
Glama
huaidj-rufus

huaidj-rufus

by huaidj

disk_details

Read-onlyIdempotent

Inspect a selected physical disk to get exact partition numbers, offsets, sizes, filesystems, and runtime formatting capabilities without formatting it.

Instructions

Read the selected physical disk, exact partition numbers/offsets/sizes, filesystems and runtime formatting capabilities. Never formats a disk.

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>"
    },
    "name": "disk_details"
  }
}

Input Schema

NameRequiredDescriptionDefault
device_numberYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description still adds real value by asserting 'Never formats a disk' as a reinforced guarantee and by disclosing what the read surfaces (partition offsets, filesystems, runtime formatting capabilities) — context not present in the annotations.

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 short sentences with zero padding. The positive capability statement is front-loaded and the safety guarantee is placed last for emphasis.

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?

With no output schema, the description carries the return-value burden and does it well by listing the categories of data returned. For a single-parameter, read-only tool this is close to sufficient; only the meaning of device_number remains under-specified.

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?

Schema coverage is 0% — device_number has only integer/0-255 constraints and no descriptive text. The phrase 'the selected physical disk' hints that the parameter selects a target disk, but the description never states that device_number is a zero-based physical disk index versus any other identifier, leaving a small but real gap.

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 uses a specific verb+resource pair ('Read the selected physical disk') and enumerates the returned content: partition numbers, offsets, sizes, filesystems, and formatting capabilities. It separates itself from write-oriented siblings with 'Never formats a disk', though it does not name the closest read alternative (disk_capabilities) explicitly.

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: 'Read the selected physical disk' plus 'Never formats a disk' signals an inspection-only call before a format operation. There is no explicit guidance on when to choose this over disk_capabilities or inspect_disk_image, nor any stated precondition.

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