Does camelAI state a plain fact or short list directly in its reply?
camelAI stated the single value in its reply, 308 orders in total, with no chart or one-cell table. Its own count query and a separate reference query on the same database both return 308.
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.
Single value stated, not chartedPassEvidence
“How many total orders have we ever received?”
We've received 308 orders in total, counting all records in the orders table. Each has a unique order ID.
Transcribed from Proof 1 · Screenshot
| ✓ | Expected: The value is stated in the reply, not returned only as a chart or a one-cell table.Found: The reply states "We've received 308 orders in total", with no chart or table; the reference query also counts 308 orders. |
The test needed the value stated in the reply; returning it only as a chart or a one-cell table would fail. camelAI answered in a sentence, and its 308 matches the reference count.
Checked order ids are unique. In the same query, camelAI also counted distinct order ids, 308, so it checked each order was unique before answering.
Many steps for one number. It took just over a minute and 12 steps to answer a one-number question, most of them reading its bundled data-analysis skill and inspecting the schema.
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 | Answer Presentation → | |
| Scenario | The answer is a plain fact or a short list → | |
| Tool | camelAI → |
Global scenario definition → · Global capability definition → · camelAI 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.