MCP tool · Orientation
diagnose
First stop for a ticket: give it the customer's identifier and the symptom (slow | down | email | ssl | dns | disk | billing) and it runs the right…
diagnose
Description
First stop for a ticket: give it the customer's identifier and the symptom (slow | down | email | ssl | dns | disk | billing) and it runs the right bundle of read-only checks and returns a ranked findings[] — each with a severity, the evidence, and a recommended fix — plus a one-line verdict. It never changes anything; act on the findings with the specific tools (request_ssl_certificate, whitelist_ip, DNS tools). A dead sub-check becomes a notes line, never an error, so a partial answer still comes back.
Input
| Name | Type | Description |
|---|---|---|
input
required
|
string |
A domain, email address, website URL, numeric service id, or hosting-account username the customer actually owns. Resolved to the owning account automatically; the resolved target is echoed back in the response.
|
symptom
required
|
enum |
What the customer reports: slow, down, email failing, ssl certificate issue, dns misconfiguration, disk full, or billing problem. One of slow, down, email, ssl, dns, disk, billing.
|
Example conversation
The site is down.
The disk quota is full on the node — wp-content/uploads is 41 GB. Want me to clear the backup folder?
Illustrative. The assistant calls diagnose behind the reply; tier
R decides whether it executes directly or returns a confirmation
link.