Skip to main content
Glama

List CephFS file systems

proxmox_list_ceph_fs
Read-only

Lists CephFS file systems with their metadata and data pools so you can inspect cluster-wide Ceph storage configuration.

Instructions

List CephFS file systems with their metadata and data pools. MDS daemons serving them are listed by proxmox_list_ceph_services.

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": "proxmox_list_ceph_fs"
  }
}

Input Schema

NameRequiredDescriptionDefault
nodeNoNode to query through (any node with Ceph installed; default PROXMOX_DEFAULT_NODE or the first online node). Results are cluster-wide.
fieldsNo
searchNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.1

TDQS

A3.8/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 and the description does not contradict it. The description adds that results include metadata and data pools, but says nothing about pagination, filtering behavior, or why idempotentHint is false for what looks like a pure read. With annotations carrying most of the burden, this is adequate but thin.

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, zero filler, with the scoping statement front-loaded and the disambiguation follow-up immediately after. Every sentence earns its place.

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?

For a three-parameter read-only list tool with no output schema, the definition covers purpose, scope, and sibling routing. The only real gap — the undocumented fields/search parameters — is a schema problem; the description itself is complete for the tool's complexity.

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

Parameters2/5

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

Schema description coverage is only 33%: the node parameter is documented in the schema, but fields and search have no descriptions anywhere. The description does not mention fields or search at all, so it fails to compensate for the coverage gap on two of three parameters.

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 opens with a specific verb and resource ("List CephFS file systems") and further scopes it as returning metadata and data pools. The second sentence explicitly delineates what this tool does NOT return (MDS daemons), routing that to proxmox_list_ceph_services, which distinguishes it from that close sibling.

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?

The boundary against proxmox_list_ceph_services is stated, giving the agent one concrete routing decision. However, there is no guidance on when to use this versus proxmox_get_ceph_status, proxmox_get_ceph_config, or proxmox_list_ceph_pools, and no prerequisites are mentioned — usage is implied rather than spelled out.

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