Can AskYourDatabase put several findings together in one response?
AskYourDatabase put the three findings into one combined chat reply, and the figures matched the earlier direct answers. The report was a formatted assistant reply, not a saved file. It reported revenue excluding cancelled orders, Home Decor as the best-selling category by units, and both order and subscription cancellation rates.
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.
Three findings assembled into one artifactPassEvidence
Input 1: “As of September 2, 2026, what was our total revenue last month?”
Input 2: “What's our best-selling product category?”
Input 3: “What's our current cancellation rate?”
Input 4: “Put all of that together into one report.”
The tool's reply is shown in the screenshot under Proof.
| ✓ | Expected: One artifact containing all of them, each still agreeing with the same question asked directly.Found: One assistant reply contained all three findings, and each figure matched the direct answer shown earlier. |
The chat was checked for one combined report that still matched the earlier direct answers. The final assistant reply contained revenue, best-selling category, and cancellation rates, and the figures matched the direct answers shown earlier.
Report in chat. The combined result appeared as a formatted chat reply, with only copy and print controls beneath it, so it was not shown as a saved file.
Extra detail included. Revenue was given after excluding cancelled orders. The answer also reported both order and subscription cancellation rates, and it noted that Furniture led on revenue.
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 · 4 tools |
| Capability | Reporting → | |
| Scenario | The user wants several findings in one place → | |
| 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.