Can Draxlr present a summary alongside its supporting details in one answer?
Draxlr answered a question about last month's revenue with a summary and its breakdown together in one reply. It stated in prose that August revenue was $14,403.87, down $3,858.77 from July's $18,262.64, and set out each of seven categories' August and July revenue and change in a table, led by furniture's $6,562.19 drop.
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 is based on this test case.
Headline figure plus its breakdownPassEvidence
“As of September 2, 2026, how did our revenue do last month, and what drove it?”
August 2026 revenue was $14,403.87, down $3,858.77 from July's $18,262.64. The drop was driven mainly by furniture (-$6,562.19), with outdoor and patio also down (-$448.84); gains in bedding and rugs (+$1,129.47) and kitchen and dining (+$803.14) partially offset it. This includes all order statuses and uses placed date.
Transcribed from Proof 1 · Screen recording at 0:06
Everything the tool returned, in order (2)
- Answer
The final response, printed above.
- Query behind the category table · not part of the answer
WITH period_bounds AS ( ... ), category_revenue AS ( SELECT o.currency, o.category::text AS category, SUM(CASE WHEN o.placed_at >= pb.last_month_start AND o.placed_at < pb.current_month_start THEN o.total_amount ELSE 0 END) AS august_2026_revenue, SUM(CASE WHEN o.placed_at >= pb.previous_month_start AND o.placed_at < pb.last_month_start THEN o.total_amount ELSE 0 END) AS july_2026_revenue ... FROM public.orders o CROSS JOIN period_bounds pb WHERE o.placed_at >= pb.previous_month_start AND o.placed_at < pb.current_month_start GROUP BY o.currency, o.category::text ) ...
| ✓ | Expected: The overall figure and its breakdown, each in a form that suits it.Found: In prose, August revenue of $14,403.87, down $3,858.77 from July's $18,262.64; then a seven-row table of each category's August and July revenue and change, in the same answer. |
The test required the overall figure and its breakdown in one answer, each in a suitable form. Draxlr gave the total in prose and the seven-category comparison as a table, and its figures agree with the store's own: August $14,403.87, July $18,262.64, furniture down from $8,549.79 to $1,987.60.
Cancelled orders counted as revenue. Draxlr counts cancelled orders as revenue and says so in its answer. Without cancelled orders, furniture still falls the most, from $5,482.52 to $1,099.30.
Dollar change only, no percentage. The prose answer gives the $3,858.77 drop in dollars but not the percentage change (-21.1%).
Table only, no chart. The category breakdown came as a table only; Draxlr produced no chart for this question.
Largest changes listed first. The category table is ordered by the size of each category's change, so the largest movers, starting with furniture, appear first.
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 test case's result says which one 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 test case's result 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 · 11 tools |
| Capability | Answer Presentation → | |
| Scenario | The answer needs a summary and its detail together → | |
| Tool | Draxlr → |
Global scenario definition → · Global capability definition → · Draxlr 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.