Skip to main content
Glama
danielrosehill

BTRFS Snapper MCP

btrfs_health

Check BTRFS filesystem health by monitoring disk usage, error statistics, scrub and balance status, and space allocation.

Instructions

Check BTRFS filesystem health and status. Monitor disk usage, errors, and maintenance operations.

Actions:

  • usage: Comprehensive filesystem space usage

  • devices: List devices in the BTRFS array

  • stats: Device error statistics (corruption, read/write errors)

  • scrub_status: Status of scrub operation (data integrity check)

  • balance_status: Status of balance operation (data redistribution)

  • df: Space allocation by data type (Data, Metadata, System)

  • filesystem_show: Filesystem information and device list

Current default mount: / Using sudo: True

Examples:

  • Check usage: action="usage", mount_point="/"

  • Check for errors: action="stats", mount_point="/"

  • Scrub status: action="scrub_status", mount_point="/"

  • Show filesystem: action="filesystem_show"

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionYesThe btrfs action: usage (space usage), devices (list devices), stats (error statistics), scrub_status (scrub progress), balance_status (balance progress), df (data/metadata usage), filesystem_show (filesystem info)
mount_pointNoBTRFS mount point (e.g., '/', '/home'). Uses default from SNAPPER_MCP_DEFAULT_MOUNT if not specified.
deviceNoSpecific device path for stats action (e.g., '/dev/sda1'). If not specified, uses mount point.
Behavior4/5

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

No annotations provided so description carries full burden. It discloses sudo usage and default mount, but doesn't explicitly state whether actions are read-only or if they can trigger side effects. Actions appear to be monitoring only, but not explicitly confirmed.

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?

Well-structured with bullet points and examples. Front-loaded with purpose. Concise yet comprehensive. Every sentence adds value.

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?

No output schema, but actions are self-explanatory. Covers key aspects like default mount, sudo requirement, and common examples. Lacks details on error handling or return format, but adequate for the tool's simplicity.

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?

Schema coverage 100%, baseline 3. Description adds significant value: explains each action in detail, provides usage examples, and clarifies the 'device' parameter usage. Exceeds baseline with rich context.

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 checks BTRFS filesystem health and status, and lists specific actions (usage, devices, stats, etc.). It distinguishes from sibling tool 'snapper' implicitly via different purpose.

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?

Provides examples for common actions and mentions default mount and sudo usage. However, lacks explicit guidance on when not to use or alternatives beyond sibling name.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/danielrosehill/BTRFS-Snapper-MCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server