Can BlazeSQL show the same answer a different way?
BlazeSQL passed this scenario: it showed the same revenue answer in a different form. In the recorded conversation, the first result appeared as a table with seven categories, then the follow-up request switched that same result to a bar chart. The bar lengths matched the table values within the chart's scale.
1 of 1 test case passed
Every test case in this scenario has a result.
The test case
Each test case is judged on its own: Pass, Fail, Not gradable, or Untested. The scenario result above counts this row.
Same answer, different representationPassEvidence
Input 1: “As of September 2, 2026, how did our revenue do last month, and what drove it”
Input 2: “Can you show that as a chart instead?”
| category | order_count | total_revenue | avg_order_value |
|---|---|---|---|
| storage_and_organization | 8 | 3775.44 | 471.93 |
| outdoor_and_patio | 3 | 3446.14 | 1148.71 |
| lighting | 5 | 3323.41 | 664.68 |
| home_decor | 7 | 3096.4 | 442.34 |
| kitchen_and_dining | 2 | 1656.05 | 828.03 |
| furniture | 2 | 1244.35 | 622.18 |
| bedding_and_rugs | 5 | 1203.23 | 240.65 |
Copied from Proof 1 · Output file (CSV), lines 1–8
Open the CSV file ↗Its contents are printed above, under What the tool returned.
Open the CSV file ↗| ✓ | Expected: The form should change, while the values stay the same.Found: A table changed to a chart, and the same seven values appeared in both views. |
The conversation first showed the revenue result as a table and then as a chart after the follow-up request. The same seven category values appeared in both forms, and the chart bars matched the table values within the chart gridlines.
No chart labels. The chart does not show numbers on the bars, so the exact figures come from the CSV and measuring against the gridlines.
Configuration and setup
How this tool was set up for the run and what the test needed in place. Each row is a fact from the run's records; a fact the records do not hold is left out, not guessed.
How this scenario is graded
How we decide Pass, Fail and Not gradable. The same rules apply to every tool tested on this scenario.
Each test case gets one result per tool: Pass, Fail or Not gradable. A test case we haven't run yet shows Untested. There are no partial results.
- Pass: the tool did everything the test expected, and nothing it said contradicts the correct answer.
- Fail: at least one expected behaviour clearly didn't happen; the row says which and quotes the tool.
- Not gradable: our evidence couldn't settle the outcome (for example a record we needed is missing). It is never counted as a fail, and the row says what's missing.
Where this sits in the benchmark
This page is one cell of a larger study: one tool, one scenario. Only this benchmark's frame appears here.
| Level | Name | Scope |
|---|---|---|
| Benchmark | AI Database Agents → | 28 scenarios · 4 tools |
| Capability | Answer Presentation → | |
| Scenario | The user asks to see the same answer a different way → | |
| Tool | BlazeSQL → |
Global scenario definition → · Global capability definition → · BlazeSQL product page →
History of this result
What has happened to this result since it was first published. Runs and grades are never overwritten: a retest or a re-grade publishes a new result and keeps the earlier one readable.
Act on this result
Nothing filed here edits the run or the grade. A challenge opens a review, and a review can produce a new run or a re-grade — which becomes the current result and leaves this one in the history.
You run the same kind of test against your own setup and get the same behaviour.
Agree →Yours behaves differently. Tell us what you got, with a screenshot if you have one.
Disagree →Something here is wrong — a reference value, a transcription, a grade.
Report an issue →Tell us what changed and we schedule a rerun of the failing test case. The old result stays as history.
Vendor notice →The same record is available as structured data through the AI Demos MCP server, with the counts, the coverage and every per-test-case reason carried as fields.
Verify the proof files
These files support this result. Open a file to inspect the original evidence.
File fingerprints (SHA-256)
A fingerprint identifies the exact file used for this result.