Skip to main content
Glama
nucleusv

Linux MCP daemon

by nucleusv
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Go
Local

disks/health

Read-onlyIdempotent

Read a drive's SMART health data as JSON to assess disk status, temperature, and attributes. Provide a bare device name like sda or nvme0n1; root access is required.

Instructions

Returns a drive's SMART data as smartctl's JSON (wraps smartctl -j -a; the smartmontools package must be installed or the call fails saying so). Read-only, but normally needs root: use privileged: true (needs a grant), since without it smartctl usually cannot open the device. device is a bare kernel name such as sda or nvme0n1, never a path; find names with disks/list. The reply is smartctl's JSON verbatim (keys such as smart_status, temperature, ata_smart_attributes or nvme_smart_health_information_log vary by drive type); a non-zero smartctl exit is not an error when it printed JSON, and virtual disks report SMART as unsupported. For I/O counters use disks/performance.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
deviceYesBare kernel device name such as 'sda' or 'nvme0n1' (never a path)
privilegedNoRun as root - required to read SMART data. Needs a grant for this tool in mcp-sudo.yaml

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.4.1
    • changedInput schema / properties / device / description
      Previous value: -"Specific block device to query (e.g., 'sda')"New value: +"Bare kernel device name such as 'sda' or 'nvme0n1' (never a path)"
    • changedInput schema / properties / privileged / description
      Previous value: -"Run as root - required to read SMART data"New value: +"Run as root - required to read SMART data. Needs a grant for this tool in mcp-sudo.yaml"
  2. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations cover the safe-read profile, and the description adds context they cannot: root is normally required, privileged:true needs a grant, failure mode when smartmontools is absent, that a non-zero smartctl exit is not an error when JSON was printed, and that virtual disks report SMART as unsupported.

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?

Dense but front-loaded with the return value first, then prerequisites, then parameter semantics, then edge cases. Slightly long, yet each sentence carries distinct operational information rather than restating structured fields.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema exists, and the description compensates by describing the return shape (smartctl JSON verbatim, keys varying by drive type) plus the error/edge-case behavior, leaving nothing an agent needs to call it correctly unaddressed.

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?

Schema description coverage is 100%, so baseline is 3, but the description adds value beyond the schema: it clarifies `device` must be a bare kernel name never a path, and explains why `privileged` is needed (smartctl usually cannot open the device without root).

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Names a specific verb, resource, and output form ('Returns a drive's SMART data as smartctl's JSON'), and clearly separates itself from siblings by routing I/O counters to disks/performance and device-name discovery to disks/list.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit when-to-use routing ('find names with disks/list', 'For I/O counters use disks/performance') and prerequisites (smartmontools installed, privileged:true with a grant). Nothing about when to reach for this tool is left to inference.

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

Deploy Server

Other Tools