mcp-openmediavault

list_filesystems

Retrieve a detailed list of all filesystems on your OpenMediaVault system, including type, label, size, usage, and mount status.

Instructions

List all filesystems on the OpenMediaVault system including type, label, size, usage, and mount status

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_filesystems"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Mar 12, 2026

TDQS

A3.9/5.0

Behavior3/5

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

The description implies a read-only operation by listing attributes, but does not disclose any behavioral traits such as performance, authentication requirements, or response format when no filesystems exist. Since no annotations are provided, the description carries the full burden, but it is only moderately transparent.

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?

The description is one sentence that is front-loaded with the action and resource, followed by the attributes. Every word is meaningful and there is no wasted text.

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 list tool with no parameters and no output schema, the description is sufficient. It tells the agent what it returns. However, it could mention that an empty list is returned if no filesystems exist, but given the simplicity, it is nearly complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has zero parameters, and the input schema covers 100% of parameters (none). The description adds value by specifying the output fields (type, label, size, usage, mount status), which provides context beyond the empty schema.

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 clearly states the tool lists all filesystems on the OpenMediaVault system, specifying the included attributes (type, label, size, usage, mount status). This distinguishes it from sibling tools like 'get_mounted_filesystems' (which likely lists only mounted ones) and 'list_disks'.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives. For example, there is a sibling 'get_mounted_filesystems' that may be more appropriate for mounted filesystems, but no indication of when to choose one over the other.

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