webmin-mcp-server

set_user_quota

Set disk quota limits for a user on a filesystem, controlling file count and disk blocks. Adjust hard/soft limits; set to 0 for unlimited.

Instructions

Set disk quota limits for a user on a filesystem. This is a dangerous operation and is blocked in safe mode. Set limits to 0 for unlimited.

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": {
      "username": "<username>",
      "filesystem": "<filesystem>"
    },
    "name": "set_user_quota"
  }
}

Input Schema

Name	Required	Description
`server`	No	Server alias (e.g., 'pi1', 'web-server'). Uses default server if not specified.
`username`	Yes	Username to set quota for
`filesystem`	Yes	Mount point of the filesystem
`hard_file_limit`	No	Hard limit for file count (0 = unlimited)
`soft_file_limit`	No	Soft limit for file count (0 = unlimited)
`hard_block_limit`	No	Hard limit for disk blocks (0 = unlimited)
`soft_block_limit`	No	Soft limit for disk blocks (0 = unlimited)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Mar 13, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Discloses that the operation is dangerous and blocked in safe mode, which is critical behavioral context. No annotations are provided, so the description compensates adequately, though it does not cover authentication requirements or return behavior.

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?

Three concise sentences: purpose, danger warning, and usage hint. No unnecessary words, front-loaded with key information.

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?

Covers the core operation, danger, and limit semantics. However, with no output schema and no annotations, it lacks information on return values, error handling, or whether the operation is immediate. Adequate but not comprehensive for a dangerous mutation 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 coverage is 100%, so baseline is 3. The description repeats the '0 = unlimited' meaning already present in schema descriptions, adding minimal new value.

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 action ('Set') and the resource ('disk quota limits for a user on a filesystem'). It is distinct from sibling tools like get_user_quota and list_user_quotas, which are read-only operations.

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?

Explicitly warns that the operation is dangerous and blocked in safe mode, and provides a usage hint ('Set limits to 0 for unlimited'). However, it does not mention alternatives or when not to use it beyond safe mode.

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

Deploy Server