Can AskYourDatabase handle company-defined terms?
AskYourDatabase stated its chosen definition of revenue rather than treating the company-defined term as unambiguous. It returned $24,944.28 based on order totals with cancelled orders excluded.
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?”
Total Revenue — 90 Days Ending September 2, 2026 Total revenue: $24,944.28 Period: June 4 – September 2, 2026 Order Status | Orders | Amount Delivered | 45 | $24,944.28 Revenue (net of cancellations) | 45 | $24,944.28 Cancelled (excluded) | 15 | $16,337.73 Notes: Revenue reflects the order totals ( total_amount ) for orders placed within the 90-day window. Cancelled orders (15 orders, $16,337.73) were excluded from revenue. If you'd prefer a different revenue basis — e.g., recognizing revenue at delivery date instead of order date, or netting out returns/refunds — let me know and I can recalculate.
Transcribed from Proof 1 · Screenshot
Every message the tool sent, in order (3)
- Revenue by order status query · not part of the answer
SELECT status, COUNT(*) AS cnt, SUM(total_amount) AS total FROM orders WHERE placed_at >= '2026-06-04' AND placed_at < '2026-09-03' GROUP BY status ORDER BY status;
- Date range and row count query · not part of the answer
SELECT MIN(placed_at) AS min_placed, MAX(placed_at) AS max_placed, COUNT(*) AS cnt FROM orders
- Revenue answer
The final response, printed above.
| ✓ | Expected: Ask which definition to use or state the definition used, rather than return an unexplained number.Found: It reported $24,944.28 from order totals, excluded 15 cancelled orders worth $16,337.73, and offered to recalculate using another definition. |
The requirement concerns disclosing the meaning used, not the accuracy of the time window. AskYourDatabase explained its calculation and exclusions rather than treating revenue as unambiguous. The answer's figures are shown, but the underlying query result grids are not.
One extra day. The revenue heading says 90 days, but the first query includes June 4, 2026, making 91 days. A 90-day window starts June 5. No orders fell on June 4, so the total was unaffected.
No refund adjustment. The revenue calculation did not subtract returns or refunds. The answer offered that adjustment as an alternative calculation.
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 | AskYourDatabase → |
Global scenario definition → · Global capability definition → · AskYourDatabase 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.