Explains the ranking in business terms by calling out the high-value customer, the highest-order-count customer, and a loyalty/upsell targeting opportunity.
What was measured
Business Insight
Does it explain what the result means?
decisive for this rankingtransformation
Explaining what the result means is part of making the database answer actually useful to a business user. (2 of 3 judges)
What was given, what came back
Test input: Best customers with unpaid-order and payment-method follow-ups · text · group: live-database-plain-english-queries
Input — what we sent
The exact prompt
Who are my best customers — the ones who order the most and spend the most? Follow-up 1: For the top 3 from that list — do any of them have unpaid orders? Follow-up 2: What payment methods do these top 3 usually use?
A conversational multi-table customer analysis with follow-up questions. It asks for the best customers by both order volume and spend, then drills into unpaid orders for the top 3 and their usual payment methods. Designed to test ranking logic, join-heavy analysis, and follow-up context retention.
Why this input is hard
- · ambiguous business term interpretation
- · multi-table joins
- · aggregation and ranking
- · follow-up context retention
- · scoping to a selected subset
- · payment behavior analysis
Output — unretouched
Also checked on this input — same tool, 5 other criteria
Ambiguity Handling◐ MixedIt states a ranking heuristic in prose, using spend as the primary sort and order count as a secondary sort, but it still leaves the no-status-filter assumption unstated and does not ask the user to clarify the two-dimensional wording.Follow-Up Context✓ WorkedCarries the same top-3 customer trio forward into both follow-ups and reuses those same three customers in the later SQL filters.Plain English Query Handling✓ WorkedAccepts the best-customers question in plain English and returns a ranked answer without requiring SQL from the user.SQL Generation✓ WorkedGenerates a clean JOIN/GROUP BY/ORDER BY/LIMIT query for the top-customers ranking, showing the database-backed answer path is functioning on this turn.SQL Visibility✓ WorkedSurfaces the generated SQL in an Executed SQL panel with Copy Code, so the query can be inspected or copied directly.
Provenance
- Observation
- 55e3e9ab-d8a7-424f-9457-f78a5dbd151f
- Evidence run
- af2abc96-3311-484b-a19d-854a2fdd2bf3
- Study
- Query Live Databases Using Plain English with AI
- Research task
- 86b9y6c99
- Tested at
- not recorded
- Source
- first-party
- Evidence state
- verified
- Proof shown
- input + output shown
- Cost / latency
- not captured
- Repeat run
- not captured
- Tester
- not captured
The last three rows are honest blanks, not placeholders — our capture has no field for them yet.
Query this
get_evidence({
tool: "futuresmart-nl2sql-agent",
scenario: "live-database-plain-english-queries"
})MCP · mcp.aidemos.com/api/mcp
Free with attribution.
Same input, same check — 7 other tools
measured on Business Insight
AskYourDatabase✓ WorkedIt adds interpretation such as Rahul Sharma being the all-rounder and Mohan Vishe being a payment-risk red flag, rather than just listing rows.Basedash✓ WorkedIt explains what the numbers mean by naming Rahul Sharma as the best overall customer, Mohan Vishe as the most frequent, and Deepak Kulkarni as the biggest spender.BlazeSQL✓ WorkedIt explains the follow-up data in business terms, including that Rahul Sharma has 1 unpaid order worth $2,199 in CONFIRMED status while Deepak Kulkarni and Karan Joshi are fully paid up.camelAI◐ MixedIt gives a one-line business takeaway by naming Rahul Sharma as the strongest frequency-and-value combination, but it stops there without any deeper interpretation or recommendation.Definite✓ WorkedIt adds useful interpretation by flagging Rahul Sharma's unpaid $2,199 order, noting it had been confirmed but unpaid since April 2025, and linking his payment methods to the issue as likely an oversight rather than a pattern.Dot✓ WorkedIt adds interpretation instead of only listing rows: Rahul is framed as the strongest all-around customer, and the tool warns that Deepak and Karan's 'usual' payment method is not yet a stable preference because each has only one order.Draxlr⚠ StruggledIt produced query descriptions, but no after-the-table narrative that distilled the result into a takeaway like which top customer had unpaid orders.
This evidence is published in
From the same study (page rebuilt from a later run)
Real inputs and real outputs, no retouching · every cell queryable via API & MCP · aidemos.com