Can AskYourDatabase handle company-defined terms?
AskYourDatabase handled the company-defined term by stating the definition it used instead of giving a bare number. It named revenue as order totals, excluded cancelled orders, and offered other bases; the answer’s heading and SQL also showed a June 4–September 2 span under a 90-day label.
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?”
The tool's reply is shown in the evidence under Proof.
| ✓ | Expected: Ask which definition to use, or state the definition applied.Found: It stated the applied definition, excluded cancelled orders, and named other revenue bases. |
The answer met the requirement to ask which definition to use or state the one applied. It chose the second path by naming revenue as order totals, excluding cancelled orders, and offering alternate bases.
Window mismatch. The answer says 90 days, but the SQL’s upper bound includes September 2.
Extra probe. A second SQL statement checked the orders table’s minimum date, maximum date, and row count before the answer.
The image shows the rendered answer, but not the result grids behind its figures.
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.