Example prompts
Name the connection, say what you want, and say whether the AI may change anything.
Tips
- Name the connection as it appears in Gadwal (“Sample Store”, “Shop – Staging”). The AI finds it with
list_connections. - Mention Gadwal in the first message of a chat (“Using gadwal, …”), so the app picks Gadwal’s tools over others.
- Say “read only” when you only want answers. The AI level enforces it anyway, but the AI won’t waste a turn proposing changes.
- Ask for one statement per change. Each one gets its own card in Review, so you can approve some and reject others.
- Ask it to wait. “Then wait for my approval and tell me what happened” makes it call
wait_for_change.
Explore
Using gadwal, describe the tables in my Sample Store connection and how they relate.
In Shop – Staging, which tables have a column with "email" in its name?
Find where the value "ORD-10442" appears in the Shop – Staging database.
Answer questions
Using gadwal on Sample Store: what were the top 5 product categories by revenue last month? Show the SQL you ran.
Explain the query plan for this query on Shop – Staging and suggest an index. Don't change anything:
SELECT * FROM orders WHERE customer_id = 42 ORDER BY created_at DESC LIMIT 20;
On the Analytics BigQuery connection, estimate what this query would cost before running it.
Propose changes
In Sample Store, set status to 'shipped' for orders 1001, 1002 and 1003. Propose it with update_rows,
then wait for my approval and tell me the result.
On Shop – Staging, add a nullable column discount_code (text) to orders. Read the table first,
propose one ALTER statement, and wait for my decision.
Write a migration on Shop – Staging that adds an index on orders(customer_id, created_at).
Safest order first, one statement per change.
Clients that show MCP prompts also offer Gadwal’s built-in Explore a database and Write a migration prompts.
WordPress
Using gadwal, show the site info for the WordPress database on Local MySQL.
Dry-run a search and replace from http://old-site.test to https://new-site.test on that WordPress
install and summarise the counts per table. Don't apply it yet.
When you’re happy with the dry run, ask it to propose the change. It always waits for your approval, and each table is backed up first.
What won’t work
- Writes on a Read-only connection: the AI gets a refusal saying so. Raise the level in Gadwal if you want it to propose changes.
- Reading a hidden column: it’s refused, by design.
- “Approve it yourself”: no tool can approve a change. Only you can, in Gadwal.