Snowflake

Snowflake_DiscoverDatabases

List the databases your role can access, newest-created first. Snowflake returns only databases your current role is granted, so this is already a per-user answer. Take a name and use it to list that database's schemas. Use name_pattern to filter server-side rather than paging the whole list.

Snowflake_DiscoverSchemas

List the schemas in a database that your role can access. List the databases first to get a valid database. Then take a schema name and list that schema's tables.

Snowflake_DiscoverTables

List the tables and views in a schema that your role can query. List the schemas first to get a valid database and schema_name, then load a table's columns before querying it. Each row's kind is TABLE, VIEW, MATERIALIZED VIEW, or SEMANTIC VIEW. A SEMANTIC VIEW cannot be read with an ordinary SELECT: it needs Snowflake's SEMANTIC_VIEW(...) syntax, which this toolkit does not support, so skip those when choosing something to query.

Snowflake_DiscoverWarehouses

List the warehouses your role can run queries on. An account usually has several, and Snowflake returns only the ones your current role is granted, so this is already a per-user answer. You only need this when a query has no warehouse to run on, either because you have no default or because you want a different one. size is the cost signal: prefer the smallest warehouse that fits the query. A SUSPENDED warehouse is still usable, since Snowflake resumes it on use by default.

Snowflake_ExecuteSelectQuery

Run a read-only SELECT query and return the rows. Only SELECT is allowed. Writes, DDL, role changes, and data movement are rejected before the query reaches Snowflake, so this tool cannot modify anything even if your Snowflake role would permit it. The query runs under your own Snowflake identity, so your role and Snowflake's row-access and masking policies decide what you can read. Two users running identical SQL can legitimately get different results. Load the table's columns before calling this, and name the columns you want rather than selecting everything. rows is positional and aligned to columns. truncated is true when more rows were available than were returned. Do not put LIMIT, OFFSET, or SQL comments in any clause; use the limit and offset parameters, which are applied for you.

Snowflake_GetTableSchema

Get a table or view's columns, so you can select exact fields. Load this before running a query, and select named columns rather than everything. Works on views as well as tables. A not-found error usually means the object is not granted to your role; re-check the table listing.

Snowflake_WhoAmI

Return the Snowflake identity every other tool uses, and the warehouse. The role is the important field. It is what decides which objects the other tools can see and which rows and cells come back, so two people calling the same tool with the same arguments can legitimately get different data. Pass current_warehouse straight through as the warehouse argument when running a query. If it comes back empty this user has no default warehouse, and a query must name one. The warehouse discovery tool lists the ones this role may use, cheapest first by size. This is the only place identity is reported. It runs no caller-supplied SQL, so what it returns is always the identity the other tools will run under.