Skip to main content
Glama
Sign In
MCP Hub

MCP Hub

by airano-ir
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

WordPress: Wp disk usage

wordpress_specialist_wp_disk_usage
Read-only

Measure WordPress site disk usage by reporting uploads, plugins, and themes sizes plus filesystem total, free, and used space for ABSPATH.

Instructions

[UNIFIED] Bytes used by uploads, plugins, and themes plus filesystem-wide disk_total/free/used for ABSPATH. Each tree walk caps at 200k files / 5s wall clock; truncated walks set truncated: true so the caller can treat the value as a lower bound. Requires Airano MCP Bridge v2.12.0+ and manage_options.

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": {
      "site": "<site>"
    },
    "name": "wordpress_specialist_wp_disk_usage"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.14.0

TDQS

A3.7/5.0
Behavior5/5

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

Annotations only declare readOnlyHint=true, so the description carries the rest and does so well: it discloses the 200k-file / 5s wall-clock cap, that truncated walks set truncated: true, and that the caller should treat such results as a lower bound. It also names the required capability and bridge version, which the annotations do not cover.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three dense sentences that each carry real information, with the measured quantities front-loaded and the truncation caveat immediately after. The only waste is the '[UNIFIED]' tag prefix, which adds no meaning for an agent.

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?

With no output schema, the description usefully enumerates the returned fields (per-area bytes plus disk_total/free/used and the truncated flag) and states the permission requirement. The one clear gap is the undocumented 'site' parameter, which is the only input the caller must supply.

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 0% and the single required parameter 'site' is never mentioned in the description. ABSPATH is referenced as the measured root, but there is no explanation of what 'site' means, what format it expects, or how it selects the root being measured.

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 names the exact resources measured: byte counts for uploads, plugins and themes, plus filesystem-wide disk_total/free/used for ABSPATH. That is specific enough to separate it from database-oriented siblings such as wp_db_size without opening the schema.

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?

It states prerequisites (Airano MCP Bridge v2.12.0+ and manage_options) but never says when to reach for this tool versus alternatives such as wp_db_size or wp_maintenance_status, nor any conditions under which it should not be used.

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