Can FutureSmart Database Agent find a complained-about exchange?
FutureSmart Database Agent can find a complained-about exchange from a vague clue. The query log shows the target row with its chat and session IDs among five queries, and the opened Activity page shows the same exchange read-only with the question, complete answer, and share-link attribution.
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.
Find a complained-about exchangePassEvidence
“How many complaints have we received on social media this month?”
The tool's reply is shown in the evidence under Proofs.
## Social Media Complaints This Month - Number of complaints received on social media: 0 The query checked the action_log table for any entries where the target contains the word "social" and the timestamp is within the current month. No such records were found, indicating that there were no complaints logged on social media during this period.
Transcribed from Proof 2 · Screenshot
| ✓ | Expected: The specific exchange can be found and inspected, including the question and response.Found: The target row appears in Query Logs with chat and session IDs, and the opened Activity page shows the same exchange read-only with the question and full answer. |
The task required the specific exchange to be found and inspected from only a rough time-and-account clue. The logs identify the row, and the opened Activity page shows that exact exchange read-only with the question and full answer, so this passes.
Answer-only view. The activity page shows the question and final answer, but no SQL or reasoning trace.
Truncated list. The query list shortens each question, so the row is identifiable there but the full text appears only after opening the exchange.
The run is not tied to a named tier.
Only five exchanges were present, so larger-volume behavior is not shown.
The list does not show each question in full.
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 | Analytics & Observability → | |
| Scenario | A user reports a bad answer and the operator has to find it → | |
| 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.