Inspect a Dataset Before Querying
Read tables and their schemas to understand the available data.
/oo Google BigQuery: Inspect dataset [dataset] in project [project]. Explain which tables and columns can answer [question].
Get a scoped answer from your warehouse without manually assembling every query.
Copy a prompt into your agent with the oo Skill installed. Add your page links and source notes before running it.
Read tables and their schemas to understand the available data.
/oo Google BigQuery: Inspect dataset [dataset] in project [project]. Explain which tables and columns can answer [question].
Execute a read-only SQL query and summarize completed results.
/oo Google BigQuery: In project [project], region [region], use table [table] to answer [question] for [date range]. Run a read-only query and summarize the completed results.
Set up oo CLI and the oo Skill in your agent.
Install OOMOL →Authorize your Google account for BigQuery.
Connect Google BigQuery →Use /oo with the pages to read, the changes to make, and where to save the result.
Connection Guide →Choose Your Agent
Inspect tables and rows, run analytical queries, and manage supported data-transfer or table operations with your Google Cloud permissions.
Browse projects, datasets, tables, and rows for analysis.
Run SQL, check jobs, and start Cloud Storage load or export jobs.
Create, revise, or delete datasets and tables, and insert rows with per-row error reporting.
List Google Cloud projects accessible to BigQuery.
google_bigquery.list_projects List BigQuery datasets in a Google Cloud project.
google_bigquery.list_datasets Retrieve BigQuery dataset metadata.
google_bigquery.get_dataset List BigQuery tables in a dataset.
google_bigquery.list_tables Retrieve BigQuery table metadata, including schema when available.
google_bigquery.get_table List rows from a BigQuery table.
google_bigquery.list_table_data Run a BigQuery SQL query and return the first page of results.
google_bigquery.query Poll a BigQuery query job and return a page of results.
google_bigquery.get_query_results Retrieve BigQuery job metadata.
google_bigquery.get_job List BigQuery jobs in a Google Cloud project.
google_bigquery.list_jobs Cancel a BigQuery job.
google_bigquery.cancel_job Start an asynchronous BigQuery query job.
google_bigquery.start_query_job Start an asynchronous BigQuery load job from Cloud Storage objects.
google_bigquery.start_load_job_from_gcs Start an asynchronous BigQuery extract job to Cloud Storage objects.
google_bigquery.start_extract_job_to_gcs Create a BigQuery dataset.
google_bigquery.create_dataset Patch BigQuery dataset metadata.
google_bigquery.patch_dataset Replace BigQuery dataset metadata with the supplied dataset resource fields.
google_bigquery.update_dataset Delete a BigQuery dataset, optionally deleting contained tables when explicitly requested.
google_bigquery.delete_dataset Create a BigQuery table.
google_bigquery.create_table Patch BigQuery table metadata.
google_bigquery.patch_table Replace BigQuery table metadata with the supplied table resource fields.
google_bigquery.update_table Delete a BigQuery table from a dataset.
google_bigquery.delete_table Insert a small batch of rows into a BigQuery table.
google_bigquery.insert_all List BigQuery routines in a dataset.
google_bigquery.list_routines Retrieve BigQuery routine metadata.
google_bigquery.get_routine Create a BigQuery routine such as a user-defined function or stored procedure.
google_bigquery.create_routine Replace BigQuery routine metadata and definition fields.
google_bigquery.update_routine Delete a BigQuery routine from a dataset.
google_bigquery.delete_routine List BigQuery ML models in a dataset.
google_bigquery.list_models Retrieve BigQuery ML model metadata.
google_bigquery.get_model Patch BigQuery ML model metadata such as friendly name, description, or labels.
google_bigquery.patch_model Delete a BigQuery ML model from a dataset.
google_bigquery.delete_model No matching tools.
Put a completed warehouse summary into a spreadsheet your team can review.
Yes. Request a dry run to validate the SQL before deciding whether to execute it.
The connected account must be able to read the selected tables and run query jobs in the project.
Manage which optional storage OOMOL can use. You can change these choices from the footer at any time.