Does FutureSmart Database Agent keep a standing exclusion rule on later questions?
FutureSmart Database Agent passed this scenario. The rule was set once, and both later answers still excluded cancelled orders in their SQL and wording.
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 counts this row.
Standing exclusion rule on later questionsPassEvidence
Input 1: “From now on, exclude cancelled orders from every revenue and order-count calculation unless I say otherwise.”
Input 2: “What's our total revenue this year?”
Input 3: “How many orders did we get last month?”
Response 1 answers Input 1.
Response 2 is the query the tool generated for Input 2; it is not part of the answer.
Response 3 answers Input 2.
Response 4 is the query the tool generated for Input 3; it is not part of the answer.
Response 5, the final response, answers Input 3.
Orders Received Last Month We received 32 orders in the most recent full month (excluding any that were cancelled).
Transcribed from Proof 3 · Screenshot
Every message the tool sent, in order (5)
- Response to input 1
Got it—I'll exclude cancelled orders from revenue and order-count calculations unless you tell me otherwise.
- Generated query for input 2 · not part of the answer
SELECT currency, SUM(total_amount) AS total_revenue FROM orders WHERE status <> 'cancelled' AND placed_at >= DATE_TRUNC('year', CURRENT_TIMESTAMP) GROUP BY currency - Response to input 2 (message 2 of 2)
Total Revenue (Year-to-Date, Excluding Cancelled Orders) The data shows the revenue generated from all orders placed since the start of the current year, excluding any orders with a status of 'cancelled'. This means the company has earned USD 51,848.02 so far this year from non-cancelled orders.
- Generated query for input 3 · not part of the answer
SELECT count(*) FROM orders WHERE placed_at >= date_trunc('month', current_timestamp - interval '1 month') AND placed_at < date_trunc('month', current_timestamp) AND status::text <> 'cancelled' - Final response
Orders Received Last Month We received 32 orders in the most recent full month (excluding any that were cancelled).
| ✓ | Expected: Both later answers respect the rule without it being restated.Found: The rule was acknowledged once. Both later answers kept excluding cancelled orders in the response and in the generated SQL. |
It is a pass, not a fail: the rule stayed in force for two later questions, and each answer still excluded cancelled orders in SQL and in the response.
Acknowledgment only. The rule-setting turn was only acknowledged and did not query the data.
Single-currency total. The yearly revenue result showed one USD row, so the total was not split by currency.
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 row says which 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 row 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 | FutureSmart Database Agent → |
Global scenario definition → · Global capability definition → · FutureSmart Database Agent 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.