Diagnostics
These abilities register when Diagnostics is detected on the site and a Pro licence is active. If either is missing the module stays absent rather than failing at call time.
At a glance
Diagnostics registers 1 ability: 1 that only read, 0 that write, and 0 marked destructive. That split is the practical answer to how much of this module can run unattended. Reads cost nothing and are safe to repeat, so discovery is the part to be generous with; the writes are where review belongs, and the destructive calls stop for an explicit confirmation every single time regardless of which profile is active.
Availability on your site
The Diagnostics module needs three things at once: WPPilot Free as the MCP foundation, an active Pro licence, and the companion plugin detected on the site. Miss any one and the module does not register, which is deliberate: an ability that appears in the tool list but fails at call time is worse than an ability that was never offered. What the connected agent can actually call is then narrowed twice more: by the safety profile active on the site, and by the WordPress capabilities of the user behind the credential. A read that succeeds for an administrator can be absent entirely for an editor.
Every write these abilities perform is recorded in the change ledger, and destructive calls can be routed through the approval queue so a person signs off before anything is applied. A successful tool result means the operation returned, not that the front end, the cache, and every dependent template are correct: that still needs a look.
Reads
Available in every safety profile, including Read Only. Inspection costs nothing and is not rate limited.
| Ability | What it does |
|---|---|
wppilot/integration-healthIntegration Health | Reports why an integration is not answering, which is otherwise indistinguishable from the ability not existing. Every Pro specialization is listed with two separate facts: whether its category is active, and whether its loader is eligible to run — a plugin present but below its version floor, or a licence gate that has not passed, shows as active and not eligible rather than silently missing. recorded_failures carries integrations whose loading threw, so one broken specialization is reported here instead of taking the rest of the plugin down with it, and request_events shows what happened during recent requests. status is degraded whenever anything was recorded. Run this before concluding an ability is unavailable: the answer is usually a gate rather than an absence, and the gate names itself. |