AI Demos Research — the structured-intelligence platform. Every verdict on these pages opens to the execution behind it.
Graded 17 October 2026

Can AskYourDatabase find a complained-about exchange?

AskYourDatabase let the admin locate and inspect the reported exchange about social media complaints. The reply said it could not access social media data and offered to count support tickets instead.

1 of 1 test case passed

Every test case in this scenario has a result.

Pass rate100%1 of 1 gradable
Coverage1 of 1test case with a result
1PassDid everything it was expected to do.
0FailNo test case failed.
0Not gradableEvery result here could be graded.
0UntestedEvery test case in this scenario has a result.
The pass rate is a summary. The evidence is the test case below: what we sent, what we checked, what the tool returned, and the proof.

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
What we sent

Input 1 · Asker account, 10/7/2026, 2:40:50 PM: “How many complaints have we received on social media this month?”

The admin account was used to open the Messages list.

Input 2 · Admin account: Typed a fragment of Person 1's email into the Messages email filter.

What the tool returned

Only the tool's reply to input 1 is copied here; its reply to input 2 was not copied as text. The rest of what the tool returned is shown in the evidence under Proof.

The reply to input 2 is in Proof 2.

Response 1, the final response, answers Input 1.

I don't have access to social media data in this database. The database contains tables for customers, orders, products, subscriptions, returns, tickets, and related records — but nothing tracking social media mentions or complaints. If you're looking for customer complaints, the closest match would be the tickets table, which tracks support issues. Would you like me to check how many support tickets were opened this month instead?

Transcribed from Proof 2 · Screenshot

Expected vs. Found
✓Expected: Locate the specific exchange and make both the user's question and the product's response available to inspect.Found: The email filter narrowed five exchanges to the user's three. Opening the social media complaints row displayed the original question and the refusal.
Supporting proof
Proof 1Screen recording
Screen recording: both users' questions, filtered by email fragment to three; opened complaints question and refusal.
Key moments
Open original ↗
Proof 2Screenshot
Screenshot: email filtering leaves one user's three questions; the opened complaints exchange shows question and refusal.
Open original ↗
Why this result

The admin found the specific exchange using only the user's identity and approximate time, as required. Both the question and response were readable, so the reported exchange could be inspected without extra clues.

Also observed in this test case

Limited search and refusal visibility. The Messages list filters by email, not time, keyword or answer status. It shows question beginnings without refusal markers, so the admin must open an exchange to identify a refusal.

Tested by Ayush Ghosh · evidence dated 7 October 2026

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.

Software that produced the output
AskYourDatabase
Build or version
Not exposed by the hosted product
Surface
Web app
Set up before the run
Two users sharing one bot first asked five questions: three from one user and two from the other. The admin had to find the social media complaints exchange knowing only who asked and roughly when.
Second account role
Member
Accounts and bot
One shared bot, two accounts on the same team; Person 1 is an admin
Tested
7 October 2026 · Ayush Ghosh

How this scenario is graded

How we decide Pass, Fail and Not gradable. The same rules apply to every tool tested on this scenario.

How results are decided

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.

The rules
  • 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.

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.

from the publication record
13 November 2026First publishedAI Database Agents v1

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.

This matches what I see

You run the same kind of test against your own setup and get the same behaviour.

Agree →
This does not match

Yours behaves differently. Tell us what you got, with a screenshot if you have one.

Disagree →
Point out an issue

Something here is wrong — a reference value, a transcription, a grade.

Report an issue →
Request a retest

On a newer build, a larger dataset, or your own setup.

Request a retest →
We have fixed this

Tell us what changed and we schedule a rerun of the failing test case. The old result stays as history.

Vendor notice →
Filed against this evidenceNothing yet. Challenges, counter-evidence and fix notices appear here with their outcome, and stay on the page after they are resolved.
Cite this result
aidemos.com/benchmarks/ai-database-agents/results/askyourdatabase/find-reported-bad-answer · 1 pass · 0 fail · coverage 1/1 · graded 2026-10-17

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.

Proof 2 · Screenshot ↗image/png · 206 KB
File fingerprints (SHA-256)

A fingerprint identifies the exact file used for this result.

Proof 1 · Screen recordingc2cace04f6d1bc6360767a3412da6cc139ddf9430c71a2fa722ffd2d30d53e07
Proof 2 · Screenshotb0bee7f4adc0c3c45c93ee66ef68835524c3037d7c0a1813bf941ad92eb086c2