Database health check (SIXTA)
sixta_health_checkTriage of diagnostics the user runs themselves. Paste any of: pg_stat_user_tables (vacuum/bloat triage, graded A–F with ready-to-run fixes), pg_settings / SHOW GLOBAL VARIABLES / conf files (configuration review against DBRE sizing rules — pass ram_gb, cpu_cores, workload), SHOW ENGINE INNODB STATUS (deadlock analysis, purge lag, buffer-pool misses, long-running transactions), or a pg_stat_statements excerpt (workload triage: dominant queries, N+1 signatures, slow-per-call outliers). Use when the user asks 'is my database healthy', mentions bloat/autovacuum/wraparound/deadlocks, or wants their config or workload reviewed. Called with nothing parseable, it returns the exact queries to run. Input is analyzed in memory and never stored.
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": {
"diagnostics": "<diagnostics>",
"engine": "<engine>"
},
"name": "sixta_health_check"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| engine | Yes | Database engine: postgresql or mysql | |
| ram_gb | No | Instance RAM in GB — enables sizing-dependent config checks | |
| version | No | Engine version, e.g. '16' (PostgreSQL major) or '8.0.35' (MySQL). Omit for a modern default; some verdicts are version-dependent and the assumption is stated in the result. | |
| workload | No | Workload shape (default mixed) — sizing rules branch on this | |
| cpu_cores | No | Instance CPU cores — enables CPU-scaled config checks | |
| diagnostics | Yes | Pasted diagnostic output (pg_stat_user_tables, pg_settings, SHOW VARIABLES, or a config file) | |
| database_xid_age | No | PostgreSQL: result of SELECT max(age(datfrozenxid)) FROM pg_database — enables wraparound checks |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| engine | No | Engine the analysis targeted, when known. | |
| report | Yes | The full human-readable SIXTA report (markdown). | |
| findings | No | Named findings as structured data, when the tool produces them. | |
| finding_count | No | Number of findings/issues identified. | |
| overall_severity | No | Highest severity across findings (Critical/High/Medium/Low/Info). |