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

Does camelAI show a trend or comparison as a visual without being asked?

camelAI answered the monthly trend question with a table and no unprompted visual. Its counts matched the database reference: June 2026 had 11 orders, July 18 and August 28.

1 of 1 test case failed

Every test case in this scenario has a result.

Pass rate0%0 of 1 gradable
Coverage1 of 1test case with a result
0PassNo test case passed.
1FailMissed at least one thing it was expected to do; the reason and proof are with each test case below.
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.

Monthly trend visualised unaskedFailEvidence
What we sent

“Show me our monthly order count for the last 3 months, as of September 2, 2026.”

What the tool returned

Using the three completed calendar months before September 2, 2026: Month (UTC) | Order count June 2026 | 11 July 2026 | 18 August 2026 | 28 Total | 57 Counts are based on orders' placed_at timestamps in customer_support_db, counting all order records regardless of status. September is excluded because it was only two days into the month.

Transcribed from Proof 1 · Screenshot

Every message the tool sent, in order (2)
  1. Answer

    The final response, printed above.

  2. Generated database query · not part of the answer
    from camelai import connections\nsql = """\nWITH months AS (\n  SELECT generate_series(DATE '2026-06-01', DATE '2026-08-01', INTERVAL '1 month')::date AS month_start\n)\nSELECT m.month_start,\n       (m.month_start + INTERVAL '1 month - 1 day')::date AS month_end,\n       COUNT(o.id)::bigint AS order_count\nFROM months m\nLEFT JOIN public.orders o\n  ON (o.placed_at AT TIME ZONE 'UTC') >= m.month_start::timestamp\n AND (o.placed_at AT TIME ZONE 'UTC') < (m.month_start + INTERVAL '1 month')::timestamp\nGROUP BY m.month_start\nORDER BY m.month_start\n"""\nprint(connections.query('customer_support_db',
Expected vs. Found
✗Expected: Produce a visual that shows change over time without being asked for one.Found: It returned a table without a visual: June 11, July 18, August 28 orders; the database reference also has 11, 18 and 28, respectively.
Supporting proof
Proof 1Screenshot
Chat screenshot: the monthly order-count question and table-only answer
Open original ↗
Proof 2Screen recording
Screen recording: the table-only answer, expanded work steps and database reference
Key moments
Open original ↗
Proof 3Screenshot
Query screenshot: the generated database query, its results and the table-only answer
Open original ↗
Proof 4Screenshot
Reference screenshot: the database's monthly order counts
Open original ↗
Why this result

On the Free web app, the database request completed successfully. Accurate figures did not satisfy the requirement to choose a visual automatically, so this was a presentation shortfall rather than an execution problem.

Also observed in this test case

Incomplete month excluded. For the monthly order-count answer, camelAI used three completed calendar months and explained that September was excluded because it was only two days into the month.

Query available for inspection. The monthly order-count answer also exposed the generated database query.

Tested by Anchal Rana · evidence dated 27 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
camelAI
Build or version
Not exposed by the hosted product · model camelCode
Plan or tier
Free
Surface
Web app
Set up before the run
Enough time periods had to be present to show a trend, and the measure had to vary across them.
Visualisation
No chart requested; settings unchanged
Tested
27 October 2026 · Anchal Rana

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.

LevelNameScope
BenchmarkAI Database Agents →28 scenarios · 11 tools
CapabilityAnswer Presentation →
ScenarioThe answer is a trend or a comparison →
ToolcamelAI →

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
16 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/camelai/trend-or-comparison-form · 0 pass · 1 fail · coverage 1/1 · graded 2026-10-27

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 1 · Screenshot ↗image/png · 279 KB
Proof 3 · Screenshot ↗image/png · 378 KB
Proof 4 · Screenshot ↗image/png · 113 KB
File fingerprints (SHA-256)

A fingerprint identifies the exact file used for this result.

Proof 1 · Screenshot3a0143ecd26e45cc83c2621c25a06cb0753bd83fa4e6ed6273965d6fb85142ce
Proof 2 · Screen recordingef0c9c670b9872109bae27924f107d2356d9dd37d08f69e87fb4a61b4729ba37
Proof 3 · Screenshotc27010ca73e4aeaed28d839bc5d2ae923f5b5b9f39bfce04e2f10d7c7d43bcf1
Proof 4 · Screenshotcaa4242678bd812d4b8ec29327e557529eef4d75ef3159cfae38d68fa5689d07