Skip to main content
Glama

WordPress: Get site health

wordpress_get_site_health
Read-only

Check WordPress site health and accessibility to retrieve comprehensive status covering WordPress, WooCommerce, and SEO plugin availability.

Instructions

[UNIFIED] Check WordPress site health and accessibility. Returns comprehensive health status including WordPress, WooCommerce, and SEO plugin availability.

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_get_site_health"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv3.13.1
    • addedInput schema / additionalProperties
      Added value: +false
  2. First observedv3.4.0

TDQS

B3.2/5.0
Behavior3/5

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

readOnlyHint=true already tells the agent this is a safe read, so the bar is lower. The description adds useful content about what areas the report covers, but says nothing about authentication requirements, latency/cost, or whether health data is cached — and 'accessibility' is left undefined.

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?

Two short sentences, front-loaded with the verb and resource; nothing is padded. The '[UNIFIED]' tag is dead weight and the second sentence could be tightened, but overall it is efficient.

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?

With no output schema, the description does carry some of the burden by naming the report's coverage areas, which is helpful. However, with a required identifier parameter completely undocumented and no statement of permission requirements, an agent can call it but cannot know what 'site' should contain.

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?

There is one required parameter, 'site', with 0% schema description coverage, so the description is the only place meaning could be added — yet it never mentions the parameter, its expected format (URL, slug, ID), or whether it selects among multiple configured sites.

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 ('Check WordPress site health and accessibility') and lists what the response covers (WordPress, WooCommerce, SEO plugin availability). It does not differentiate itself from the near-identical sibling 'wordpress_site_health', and the '[UNIFIED]' prefix adds no meaning.

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 purpose: an agent can infer this is a diagnostic call, but there is no explicit when-to-use, no prerequisite, and no guidance on choosing between this and the closely-named wordpress_site_health or wordpress_diagnose_site 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