Does Draxlr say which definition it uses for a company-defined term?
Draxlr answered that revenue over the 90 days to September 2, 2026 was $39,806.75 and said in the same answer that it used all order statuses. Its explanation and generated query match that stated choice, which counts cancelled orders as revenue.
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.
Revenue asked by the company's own wordPassEvidence
“As of September 2, 2026, what was our total revenue over the last 90 days?”
As of September 2, 2026, total revenue over the last 90 days was $39,806.75. This uses all order statuses.
Transcribed from Proof 1 · Screen recording at 0:00
Everything the tool returned, in order (3)
- Answer
The final response, printed above.
- Query behind the answer (SQL tab) · not part of the answer
SELECT COALESCE(SUM(total_amount), 0) AS total_revenue FROM public.orders WHERE placed_at >= (DATE '2026-09-02' - INTERVAL '90 days') AND placed_at < (DATE '2026-09-02' + INTERVAL '1 day')
- Explanation panel
It uses all order statuses because no status filter was specified.
| ✓ | Expected: Either ask which definition of the company's term to use, or state the definition applied; a bare number treated as unambiguous fails.Found: It answered $39,806.75 and stated it used all order statuses; its explanation gives the same choice, and its generated query has no status filter. |
It is a Pass: the test fails a bare number given as though the company's word were unambiguous, and Draxlr instead stated the definition behind its figure, all order statuses, in the answer and again in the explanation, matching its query.
Cancelled orders counted. The chosen definition counts cancelled orders: 15 of the 57 orders in the window are cancelled, worth $16,337.73, and excluding them gives $23,469.02. Draxlr disclosed its choice but did not offer that alternative.
Literal reading. Its stated reason, "because no status filter was specified", reads the question literally rather than as a term the company might define.
An extra day. The revenue query included June 4, covering 91 days rather than 90. No orders fell that day, so the total was unaffected.
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 | Question Answering → | |
| Scenario | The question uses a term the company defines itself → | |
| 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.