Can Kommunicate show an agent's tool call in a conversation?
Kommunicate did not show the inspected order-lookup tool call. In both opened conversations, the thread showed only the customer message and the reply; one reply included live order details, but no tool, function, or API entry appeared, and the events panel stayed collapsed.
1 of 1 test case failed
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.
See the order-lookup tool callFailEvidence
We opened the existing order-lookup conversations and looked for the tool call. Nothing was sent to the product.
The tool's response has no text to quote: it is what the evidence under Proof shows.
Proof 1 · Screen recording · ▶ 0:50–0:52; ▶ 1:50–1:52
| ✗ | Expected: Show that the order-lookup call happened.Found: The opened threads show the customer message and reply, but no tool, function, or API entry is visible; the events panel stays collapsed. |
It is a fail because the requirement was to show that the order-lookup call happened, but the opened conversations show only the customer and reply messages. One reply contains live order data, yet the call itself is not rendered, and the events panel was never opened.
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 Customer Support Chatbots → | 26 scenarios · 14 tools |
| Capability | Analytics and observability → | |
| Scenario | Agent actions/tool calls can be inspected → | |
| Tool | Kommunicate → |
Global scenario definition → · Global capability definition → · Kommunicate 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.