Skip to main content
Glama
Sign In
mx-route-mcp

mx-route-mcp

by MauiGrowth
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Get disk usage and quota

get_quota
Read-onlyIdempotent

Check an MXroute account's disk usage: bytes used, quota limit, percent used, category breakdown, and grace-period status if over quota.

Instructions

Returns the account's overall disk usage: bytes used, quota limit in bytes (0 = unlimited), percent used, a breakdown by category (email, web, databases, backups, other) and grace-period status if over quota. Figures are refreshed hourly by MXroute.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), so the bar is lower. The description still adds real value beyond them: '0 = unlimited' decodes a sentinel quota value, grace-period status is disclosed as conditional, and 'refreshed hourly by MXroute' tells the agent the data's freshness, which prevents it from treating results as real-time.

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 that front-loads the primary return ('overall disk usage') and then details the fields. No filler or repetition of the title.

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?

With no output schema, the description carries the full burden of describing return values, and it does so thoroughly — all key fields, the unlimited sentinel, category breakdown, and grace-period condition. Nothing an agent needs in order to call this zero-argument tool correctly is missing.

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?

Zero parameters, so there is nothing to document and the baseline of 4 applies. The description correctly focuses on output content instead.

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?

States a specific verb and resource ('Returns the account's overall disk usage') and enumerates exactly what comes back: bytes used, quota limit, percent used, category breakdown, grace-period status. The word 'overall' implicitly separates it from the per-mailbox get_email_usage sibling, but no sibling is named, so differentiation is inferred rather than stated.

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?

There is no explicit when-to-use statement, no prerequisites, and no reference to alternatives such as get_email_usage or list_packages. Usage is only implied by the tool's name and content.

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