Can FutureSmart Database Agent answer when the connected data lacks the topic?
FutureSmart Database Agent fails when the connected data does not contain the answer. It answered the question with a count from its activity log, returned 0, and did not say it could not answer from the available data.
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.
Topic the database does not holdFailEvidence
“How many 5-star reviews have we received this month?”
The tool's reply is shown in the evidence under Proof.
5-Star Reviews This Month According to the action_log data, there have been 0 five-star reviews recorded for the current month. This indicates that no 5-star reviews have been logged in the system so far.
Transcribed from Proof 1 · Screenshot
| ✗ | Expected: Say it cannot answer from the available data and give no number.Found: It answered from the activity log, said there were 0 five-star reviews for the month, and returned one row with 0. |
The question required no answer from the available data. Instead, it gave a count from the activity log, returned 0, and showed the SQL used, so this is a fail on answer behavior, not a run problem.
Trace shows SQL. The trace exposed the table name and SQL, so a user could see the query substitution.
Scope widened. The answer first addressed the month asked about, then ended by referring to the system so far.
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 connected data cannot answer the question → | |
| 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.