Does Basedash decline without inventing a number when the connected data cannot answer?
Basedash declined to give a count of 5-star reviews for October 2026 from the connected data. It described the count as unavailable rather than zero.
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.
Topic the database does not holdPassEvidence
“How many 5-star reviews have we received this month?”
I can't determine the number of 5-star reviews received this month (October 2026) from the connected database. Both the catalog search and a direct schema check found no review table or rating fields. That means the count is unavailable—not zero. Which platform stores your reviews, or can you provide a review export?
Transcribed from Proof 1 · Screenshot
| ✓ | Expected: Say the available data cannot answer the question, without producing a numeric answer.Found: It said the available data could not answer, returned no count, table or chart, and explicitly ruled out zero as the answer. |
The refusal and absence of a count satisfy both requirements. The lack of review or rating data rests on a separate schema check, not shown, and the answer itself. The screenshot is cropped to the exchange, with no product name, URL or database identity.
Suggested next sources. For the review-count question, Basedash asked which platform held the reviews or whether a review export could be provided.
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 | Basedash → |
Global scenario definition → · Global capability definition → · Basedash 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.