Can FutureSmart Database Agent answer questions that use business-defined terms?
FutureSmart Database Agent answered a company-defined revenue question by stating the definition it used instead of giving only a bare number. The answer block and generated SQL use the same 90-day, not-refunded definition, and the capture shows the matching USD total.
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.
Revenue asked by the company's own wordPassEvidence
“As of September 2, 2026, what was our total revenue over the last 90 days?”
Total Revenue (Last 90 Days as of September 2, 2026) Currency: USD Total Revenue: USD 57,038.91 This figure represents the sum of all order amounts placed between June 4, 2026 and September 2, 2026 that have not been refunded.
Transcribed from Proof 1 · Screenshot
| ✓ | Expected: Either asks which definition to use, or states the definition it applied.Found: It stated the definition it used, and the query matched that wording instead of giving only a bare number. |
It passes because the customer asked about a company-defined term, and the product stated the definition it applied instead of returning only a number. The answer and SQL match on the 90-day window and excluding refunded orders.
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 question uses a term the company defines itself → | |
| 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.