Skip to main content
Glama

mcp_get_health

Retrieves a WordPress site’s health status and score, highlighting debug mode, missing HTTPS, and pending updates so you can identify issues quickly.

Instructions

Get a quick site health status and score (100 minus 20 per issue: WP_DEBUG on, no HTTPS, pending updates)

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

Input Schema

NameRequiredDescriptionDefault
siteYesSite id (see list_sites)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv3.4.0
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / site
      Added value: +{
      +  "description": "Site id (see list_sites)",
      +  "type": "string"
      +}
    • addedInput schema / required
      Added value: +[
      +  "site"
      +]
  2. First observedv2.0.0

TDQS

B3.3/5.0
Behavior2/5

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

No annotations exist, so the description carries the full behavioral burden. It discloses the score formula and names the three issues checked, which is genuinely useful, but it omits that the check set is limited to those three (a site can pass with other problems), does not confirm the operation is read-only, and says nothing about permissions or cost.

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?

A single sentence with the outcome front-loaded and the scoring rule in a compact parenthetical. Dense but every clause carries information; no filler or restatement of the tool name.

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?

For a one-parameter read tool with no output schema, the description adequately covers what is returned (status plus a numeric score) and how that score is computed. The main remaining gap is that it never says the three listed issues are the only checks performed.

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?

Only one parameter with 100% schema description coverage ('Site id (see list_sites)'), so the schema already does the work and the baseline is 3. The description adds nothing about the site parameter itself, though its absence of extra detail is not a real loss here.

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 — get site health status and score — and goes further by spelling out the scoring formula. It does not explicitly contrast with siblings like mcp_get_plugins_health or mcp_get_system_info, but the narrow scope is clear from the enumerated checks.

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?

The word 'quick' implies a lightweight triage check as opposed to deeper diagnostics, which is a useful implicit signal. However, there is no explicit statement of when to prefer this over mcp_get_plugins_health, mcp_get_debug_info, or mcp_get_system_info, and no exclusions or prerequisites.

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