mxroute-mcp

Get Disk Quota

get_disk_quota

Read-onlyIdempotent

Retrieve MXroute account disk usage and quota limits, including percent used, category breakdown, and over-quota grace period to monitor storage capacity.

Instructions

Returns account disk usage: total bytes used and quota limit (0 = unlimited), percent used, a category breakdown (email, web, databases, backups, other — in bytes), and the grace period when the account is over quota. Data is refreshed hourly.

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`username`	Yes
`breakdown`	Yes
`total_used`	Yes
`updated_at`	Yes
`total_limit`	Yes
`grace_period`	Yes
`percent_used`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 8, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds two genuinely useful behavioral facts beyond that: results can be stale because 'Data is refreshed hourly', and a quota limit of 0 means unlimited, which prevents misreading the return value.

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?

A single sentence, front-loaded with the verb and resource, where every clause carries information (sentinel value, category list units, grace period, refresh cadence). Nothing is redundant or padding.

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 zero-parameter read-only tool with an output schema and full annotations, the description covers what an agent needs: what comes back, the meaning of the 0 sentinel, and the hourly staleness window. Little is left to inference.

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

Parameters4/5

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

The tool takes zero parameters, so the baseline is 4 and there is no parameter meaning for the description to add. It correctly avoids inventing inputs and instead spends its words on output semantics.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Uses a specific verb+resource ('Returns account disk usage') and enumerates the data returned: total used, quota limit with 0=unlimited sentinel, percent used, category breakdown, and grace period. This makes it distinguishable from the narrower get_email_usage sibling, though it never names that sibling explicitly.

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?

Usage is only implied by the tool's scope — an agent can infer it should call this for account-wide quota checks. There is no explicit when-to-use or when-not guidance, and no routing to get_email_usage for email-only usage figures.

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

Deploy Server