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

Does Draxlr show a trend as a chart without being asked?

Draxlr answered a monthly order-count question with a sentence and a three-row table, and drew no chart. Its Visualization pane, shown by default, held a table of the three months with no axes, bars or line.

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

Monthly order count was 11 in Jun 2026, 18 in Jul 2026, and 28 in Aug 2026. This covers the last 3 complete calendar months as of September 2, 2026.

Transcribed from Proof 1 · Screen recording at 0:03

Everything the tool returned, in order (3)
  1. Answer

    The final response, printed above.

  2. Generated query (SQL tab of the result panel) · not part of the answer
    WITH months AS (
      SELECT generate_series(
        date_trunc('month', DATE '2026-09-02') - INTERVAL '3 months',
        date_trunc('month', DATE '2026-09-02') - INTERVAL '1 month',
        INTERVAL '1 month'
      ) AS month_start
    )
    SELECT
      to_char(months.month_start, 'Mon YYYY') AS month,
      COUNT(public.orders.id) AS order_count
    FROM months
    LEFT JOIN public.orders
      ON public.orders.placed_at >= months.month_start
      AND public.orders.placed_at < months.month_start + INTERVAL '1 month'
    GROUP BY months.month_start
    ORDER BY months.month_start
  3. Explanation shown with the generated query (SQL tab), not part of the answer

    This returns order counts by month for the last 3 complete calendar months as of September 2, 2026, covering Jun 2026 through Aug 2026. Months with zero orders are included.

Expected vs. Found
✗Expected: A visual whose form shows change over time, produced without being asked for one.Found: An answer sentence and a result card labelled 'Table - 3 rows'; the default Visualization tab shows a table of three month rows with no axes, bars or line.
Supporting proof
Proof 1Screen recording
Screen recording: the question, the answer with its table card, and the Visualization and SQL tabs
Key moments
Open original ↗
Why this result

The test requires a visual showing change over time, produced without being asked. The question did not ask for one, and the pane where a chart would appear, shown by default, held a table. A chart reached only by picking a chart type is a request, so it does not count.

Also observed in this test case

Correct monthly counts. The answer's counts, 11, 18 and 28 orders for June, July and August 2026, match a reference query against the same database.

Read as three completed months. Draxlr read 'the last 3 months' as June to August, the three completed calendar months, leaving out 1 and 2 September, and said so in its answer.

No time zone stated. The month boundaries follow the database's time zone, UTC here, and the answer does not state a time zone.

Tested by Ayush Ghosh · evidence dated 22 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
Draxlr
Build or version
Not exposed by the hosted product
Plan or tier
Premium
Model
gpt-5.5-1
Surface
Web app
Set up before the run
Three completed months were needed so change over time could appear, and the measured value had to vary across them.
Visualization choice
none made
Tested
22 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.

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

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

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.

Proof 1 · Screen recording320fb03e36711499459b90ff8329f2ed56ecd0bb1bccd230ba77e413f9572c02