Health and performance · stop 2 of 13
db_health_check
Checks for common problems and reports them.
Works in read modeTool sets: dba · full
You might ask
“Run a health check.”
Your assistant may call db_health_check to answer.
How it works
- Cache hit ratio, tables with many dead rows that need vacuuming, connection use and blocking locks. Sections fail independently.
Parameters
None. Call it as it is.
What your assistant reads
The description nexql-mcp sends with the tool. It's how the assistant decides when to use it.
Run a database health overview: size/connection stats, cache hit ratio, tables with dead tuples needing vacuum, active connections, and blocking-lock count. Sections that fail are reported individually; partial results are still returned.