Does Draxlr suggest what to ask next after answering a database question?
Draxlr answered the revenue question without suggesting what to ask next. Its chat left the user to write a follow-up rather than offering a question based on the analysis.
1 of 1 test case failed
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.
Suggested next questions after an answerFailEvidence
Input 1 · Initial revenue question: “As of September 2, 2026, what was our total revenue last month?”
Input 2 · Revenue measure clarification: “Order total_amount”
Clarifying question about revenue
Which revenue should I total for last month?
Revenue answer
Total revenue last month was $14,403.87. This covers August 2026 across all order statuses.
Transcribed from Proof 1 · Screen recording at 0:01
Everything the tool returned, in order (3)
- Clarifying question about revenue
Printed above.
- Revenue answer
The final response, printed above.
- SQL behind the revenue answer · not part of the answer
SELECT COALESCE(SUM(CAST(total_amount AS NUMERIC)), 0) AS total_revenue FROM public.orders WHERE placed_at >= TIMESTAMPTZ '2026-08-01 00:00:00+00' AND placed_at < TIMESTAMPTZ '2026-09-01 00:00:00+00'
| ✗ | Expected: At least one unprompted follow-up question that builds on the analysis and can be answered from the database.Found: No suggested question appeared after the revenue answer. The chat offered a result card and a composer for the user to type another question. |
Draxlr answered a question about a specific measure and period, but has no feature for suggesting follow-up questions. The missing capability makes this a failure to meet the requirement, not an untested interaction; neither its settings nor its documentation offers a way to enable it.
Clarification before the answer. Before answering the revenue question, Draxlr asked the user to choose among four interpretations of revenue based on the database.
Revenue scope and transparency. The August 2026 revenue answer included all order statuses and showed its SQL. It returned $14,403.87; the independently calculated reference total was also $14,403.87.
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 | Conversational Interaction → | |
| Scenario | The agent offers what to ask next → | |
| 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.