Skip to main content
Glama

Get disk SMART data

proxmox_get_disk_smart
Read-only

Retrieve a disk's SMART health status and attributes, including ATA tables or NVMe/SAS text reports, to monitor drive reliability and detect failures.

Instructions

Get a disk's SMART health and attributes (ATA attribute table, or the text report for NVMe/SAS).

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": {
      "disk": "<disk>"
    },
    "name": "proxmox_get_disk_smart"
  }
}

Input Schema

NameRequiredDescriptionDefault
rawNoReturn the full unprocessed objects from the API (larger)
diskYesBlock device path, e.g. "/dev/sdb" (see proxmox_list_disks)
nodeNoNode name. Defaults to PROXMOX_DEFAULT_NODE, or the only node on a single-node install. See proxmox_list_nodes.
health_onlyNoOnly return the overall health status

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.1

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds real value beyond them by disclosing that the returned payload differs by device type (structured ATA attribute table vs. free-text report for NVMe/SAS), but it omits failure modes such as disks that do not support or do not have SMART enabled.

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 front-loaded sentence with no filler; the parenthetical earns its place by clarifying the return format difference across device types.

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 burden of explaining return values, and it does so at a high level (attribute table vs. text report). Combined with fully documented parameters and read-only annotations, only minor gaps remain, such as error behavior for non-SMART devices.

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 description coverage is 100%, with each of the four parameters documented in-schema (disk path, node defaulting, raw, health_only). The description adds no parameter-level meaning, so the baseline of 3 applies — the schema does the heavy lifting here.

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?

Specific verb+resource (get a disk's SMART health and attributes) with a clear statement of what the response contains, including the device-type-dependent shape (ATA attribute table vs. text report for NVMe/SAS). It does not explicitly name a sibling, though the resource is narrow enough (single disk SMART) to be distinguishable from list/status tools.

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: the description makes it evident this is a diagnostic read used to inspect a specific disk's health, but it states no when-to-use conditions, no prerequisites (e.g., SMART enabled on the device, smartctl availability), and no alternatives for bulk disk inventory or health overviews.

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