Use the connected host's SQL query tool: prefer
from the
SQL Tools MCP server that ships with the
plugin, or an
already authorized SQL CLI connection. If that server is not connected or lists
no connections, follow the
skill, which asks before
installing or configuring anything. Verify the selected server/database and
permissions before interpreting absence as a finding.
If the catalog exposes
getEstimatedShowplanForQuery
, it can resolve a complete
statement's optimizer hash without executing the workload. Compilation can still
require permissions, locks and auto-statistics work; skip it when the requested
scope prohibits those effects. Otherwise use the reference's text-search path
and report ambiguity. Do not send
or rely on SET state across independent
raw-query calls. No tool available means provide the diagnostic SQL and identify
what remains unobserved.
Return query identity and uncertainty, cache observations, historical coverage,
plan differences, and the next smallest useful investigation. When delegated,
preserve the caller's requested scope and output format.