Skip to main content
Glama

Scan for storage

proxmox_scan_storage
Read-only

Scans available NFS exports, CIFS shares, PBS datastores, iSCSI targets, and local LVM/ZFS pools to identify storage you can add to Proxmox VE.

Instructions

Discover storage that can be added with proxmox_save_storage: NFS exports or CIFS shares on a server, PBS datastores, iSCSI targets on a portal, or local LVM volume groups, LVM thin pools and ZFS pools on a node. The nfs, cifs, pbs and iscsi scans make the node contact the given server, possibly with credentials, so they need write access (PROXMOX_ALLOW_WRITES=true); the local scans are always available.

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": {
      "type": "<type>"
    },
    "name": "proxmox_scan_storage"
  }
}

Input Schema

NameRequiredDescriptionDefault
vgNolvmthin: volume group to list thin pools of
nodeNoNode name. Defaults to PROXMOX_DEFAULT_NODE, or the only node on a single-node install. See proxmox_list_nodes.
portNopbs: port (default 8007)
typeYesWhat to scan for
domainNocifs: SMB domain/workgroup
portalNoiscsi: portal IP or name, optionally with :port
serverNonfs/cifs/pbs: server name or IP
passwordNocifs/pbs: password or token secret (required for pbs)
usernameNocifs/pbs: user name (pbs: user@realm or token ID; required for pbs)
fingerprintNopbs: server certificate fingerprint

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.1

TDQS

A4.1/5.0
Behavior4/5

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

Beyond the annotations, it discloses genuinely useful behavior: nfs/cifs/pbs/iscsi scans make the node contact the given server (network egress), may carry credentials, and are gated behind PROXMOX_ALLOW_WRITES=true, while lvm/lvmthin/zfs are always available. This adds real context not present in readOnlyHint/openWorldHint/idempotentHint. Minor tension exists with openWorldHint=false and readOnlyHint=true (remote scans reach out to arbitrary servers and require the writes flag), but that flag governs Proxmox state mutation rather than the connection, so it is not a direct contradiction.

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 sentences, no filler: the capability and its scan types come first, the access requirement and its exception second. Every clause carries information an agent needs before calling.

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?

There is no output schema, so the description would ideally hint at what a scan returns (candidate exports/targets/pools, and how to feed that into proxmox_save_storage), but it only names the downstream tool. The access gating is covered well, yet result shape and failure modes (unreachable server, bad credentials) are left unstated for a 10-parameter tool.

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%, so each of the 10 parameters is already documented, which sets the baseline at 3. The description adds only a coarse mapping (which scan types involve a server/portal versus a node) and does not explain vg, node, port, fingerprint, or credential usage beyond noting credentials may be involved.

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?

The description uses a specific verb (Discover) plus the resource (storage that can be added), then enumerates the seven scan types by name (NFS, CIFS, PBS, iSCSI, LVM, LVM-thin, ZFS) and names the follow-up tool proxmox_save_storage. An agent can distinguish this discovery tool from the list/get storage siblings purely from the text.

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

Usage Guidelines4/5

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

It makes clear this is for finding storage that is not yet configured ("that can be added with proxmox_save_storage"), which implicitly separates it from proxmox_list_storage/proxmox_get_storage, and it states the prerequisite for the four remote scans (PROXMOX_ALLOW_WRITES=true) versus the always-available local scans. It stops short of an explicit "use this instead of X when Y" statement or noting credential requirements per type beyond a general mention.

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