Can AskYourDatabase consistently follow a standing rule across future answers?
AskYourDatabase passed this scenario: a standing rule carried into later, unrelated answers. The exclusion was entered in Documentation once, and both later replies used it in the generated query and in the answer text.
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.
Standing exclusion rule on later questionsPassEvidence
Input 1: “What's our total revenue this year?”
Input 2: “How many orders did we get last month?”
Response 1 is a progress message the tool sent for Input 1; it is not part of the answer.
Response 2 is the query the tool generated for Input 1; it is not part of the answer.
Response 3 answers Input 1.
Response 4 is the query the tool generated for Input 2; it is not part of the answer.
Response 5, the final response, answers Input 2.
You received 89 orders last month (September 2026, excluding cancelled orders)
Transcribed from Proof 3 · Screenshot
Every message the tool sent, in order (5)
- Progress message for input 1
I'll look up the total revenue for this year (2026), excluding cancelled orders.
- Generated query for input 1 · not part of the answer
SELECT COALESCE(SUM(total_amount), 0) AS total_revenue FROM orders WHERE status <> 'cancelled' AND placed_at >= '2026-01-01' AND placed_at < '2027-01-01'
- Response to input 1 (message 3 of 3)
Your total revenue this year (2026, excluding cancelled orders) is $151,064.66.
- Generated query for input 2 · not part of the answer
SELECT COUNT(*) AS order_count FROM orders WHERE status <> 'cancelled' AND placed_at >= '2026-09-01' AND placed_at < '2026-10-01'
- Final response
The final response, printed above.
| ✓ | Expected: Both later answers respect the rule without it being restated.Found: The saved rule stayed in effect for both later questions: each reply used the exclusion and changed the totals. |
A standing rule had to carry into later answers. It was entered once in Documentation, and both later replies kept the exclusion and changed the totals, so the later questions were answered under the rule.
Rule visible. Each answer stated the exclusion in words, so the rule was visible without reading the query.
Date window used. The product treated this year as 2026 and last month as September 2026.
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 | Training → | |
| Scenario | The user sets a standing rule for all future answers → | |
| 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.