Does FutureSmart Database Agent let the same answer be shown a different way?
FutureSmart Database Agent failed to keep the same answer when asked for a different presentation. The follow-up returned the same table and said it could not render a chart, while an earlier turn in the same conversation showed a bar chart for the same data; the later turn's values also differed from the earlier chart.
1 of 1 test case failed
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.
Same answer, different representationFailEvidence
“Can you show that as a chart instead?”
The tool's reply is shown in the evidence under Proofs.
Response to input 1 (message 1 of 3) While I cannot render a visual chart here, the table above provides a clear, ordered view of the revenue distribution across categories for the last month. Response to input 1 (message 2 of 3) The lowest-earning category is bedding_and_rugs, generating just $1,203.23. Response to input 1 (message 3 of 3) SELECT category, currency, SUM(total_amount) AS total_revenue FROM orders WHERE placed_at >= '2026-08-01 00:00:00+00' AND placed_at < '2026-09-01 00:00:00+00' GROUP BY category, currency ORDER BY total_revenue DESC
Transcribed from Proof 3 · Screenshot
Transcribed from Proof 3 · Screenshot
Transcribed from Proof 4 · Screenshot
| ✗ | Expected: The form should change while the values stay the same.Found: The follow-up kept the table and said it could not render a chart, but the values changed from the earlier chart because the refund filter was absent. |
The answer had to change form without changing values. Instead, the follow-up kept the table and said it could not render a chart, and the earlier chart for the same data showed different values because the refund filter was missing here.
Share mismatch. The claimed 16% share does not fit the shown numbers; it is closer to 28%.
Request read back. The trace strip shows the product read the chart request before answering.
The comparison with the earlier turn is not shown in the graded turn alone.
The follow-up capture does not show the toggle row.
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 | Answer Presentation → | |
| Scenario | The user asks to see the same answer a different way → | |
| 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.