Growth Nirvana Bundle Query
Purpose
Answer questions from bundle files first, then optionally run live queries via MCP.
Workflow
- Resolve dataset by matching
dataset/dataset.json.displayName. - Select reporting model:
- inspect
models/combined_report*and related downstream models - choose
combined_reportor variant (combined_report_ff,combined_report_catalog, etc.)
- inspect
- Validate fields in:
warehouse/tables/<selected_table>/fields/*.json
- Build SQL based on validated fields.
- If execution is needed:
- run
create_query_execution - fetch with
get_query_execution(include=results, row_limit=...)
- run
- Return answer with evidence and rationale.
Guardrails
- Do not assume
cost; verify_cost/cost. - If variant logic changes semantics (for example Meta/Bing/X remaps), state that clearly.
- If no rows returned, provide date-coverage diagnostic query.
Response Contract
workflow: bundle-query@v1- dataset and selected model/table
- answer summary
- SQL used (or summary)
- execution id/run state when executed
- result rows summary and truncation flag when requested
- evidence paths and caveats
Resources
- Query templates: common-queries.md
- Usage examples: examples.md
- Troubleshooting: troubleshooting.md