Skip to main content
Glama

WordPress: Site health

wordpress_site_health
Read-only

Retrieve a unified WordPress site health snapshot in one request to check PHP/MySQL versions, active plugins and theme, server details, disk space, and writability.

Instructions

[UNIFIED] Unified site-health snapshot via the airano-mcp-bridge companion plugin (v2.6.0+). Single request returns WP + PHP + MySQL versions, loaded PHP extensions, server software + disk free, active plugins with versions, active theme, and writability checks. Falls back to companion_available: false when the plugin is missing. Requires 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_site_health"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.13.1

TDQS

B3.2/5.0
Behavior3/5

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

readOnlyHint=true already establishes the safety profile, so the bar is lower; the description still adds real context: the dependency on the airano-mcp-bridge plugin v2.6.0+, the manage_options capability requirement, and the explicit degraded-path behavior ("companion_available: false" when the plugin is missing). It does not describe response shape beyond a field list or whether the call is cached/rate-limited.

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 compact sentences, front-loaded with the capability and immediately followed by the return payload, dependency, and auth requirement. The bracketed "[UNIFIED]" marker and plugin-version detail are slightly noisy but each sentence carries distinct information.

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 takes on the burden of describing returns and does so thoroughly, including the failure mode when the companion plugin is absent. For a single-param read-only snapshot tool the only real gap is the undocumented site argument.

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?

There is one required parameter, site, and schema description coverage is 0%, so the schema carries no meaning at all. The description never mentions site or its expected format (ID, slug, URL), leaving the agent to guess. It partially compensates by describing what the call returns and its prerequisites, but the sole input remains undefined.

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?

The description names a specific verb and resource ("unified site-health snapshot") and enumerates the concrete data returned — WP/PHP/MySQL versions, extensions, server software, disk free, plugins, theme, writability checks. That is far more specific than a restated title. It does not, however, differentiate itself from siblings like wordpress_get_site_health or wordpress_diagnose_site, which an agent would need to choose between.

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 when-to-use or when-not-to-use guidance and no named alternative, only the prerequisite "Requires manage_options." An agent can infer it is a diagnostic read, but nothing tells it when to prefer this over the similarly named health siblings.

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