Use documentation safely with a SQL assistant ​

Use the public Coordinator DB documentation as the reference when an assistant helps write SQL or explain an error. Start with the relevant statement, type or interface page and include the exact task. A named feature in another product is not evidence that Coordinator DB accepts its syntax.

Coordinator DB does not document a bundled documentation MCP server. An assistant can still work from the published pages you provide. Ask it to cite the relevant public contract and to distinguish proposed SQL from a command that was actually executed.

For a query task, provide a minimal schema, representative synthetic rows, expected output and the complete error message. Remove credentials, private row values and unrelated server output. Begin with a read-only SELECT or EXPLAIN QUERY PLAN when investigating access choices.

Review data-changing statements before execution. EXPLAIN ANALYZE is not a read-only substitute for a write: it executes the statement once. Transaction controls can help test changes, but their connection scope must be correct, especially over HTTP.

See SQL statements, types, EXPLAIN and transactions.