Read one database’s schema: its tables with their quoted sqlName, version and saved views, and each table’s columns with their SQL names, types (with the kind of an entity column, USER for a person column), whether they hold several values, the labels a select column accepts, the target table of a relation, and the types the column can change to. Call this before writing SQL for a database you have not already described in this conversation. Guessing table or column names is the single most common way a query fails, and the schema is small. Get the databaseId from ListDatabases. QueryDatabase describes the SQL dialect.