Loading workspace…
How your tools get used
Customer workflows · 6 runs · Records tool cohort
B04 · Latest batch
- Tools provided
- 83% Confirmed in 5 of 6 runs
- MCP used
- 0% 0 of 6 runs called a tool
- Tools called
- 0 / 4 Across the whole batch
- Without MCP calls
- 6 Runs with no recorded MCP use
From availability to use
Two independent measurements over the same 6 runs. Their overlap is not shown.
Availability
5 runs confirm tool definitions were supplied. The remaining 1 have unknown availability.
Consideration
Supplying definitions does not show that an agent considered a tool. That decision is unobserved.
Recorded use
0 runs contain a tool call. The 6 without calls need prompt and response context to interpret.
Which tools get called
Runs can use more than one tool. Run counts below are not additive.
| Tool | Calls | Runs using tool | Run use rate | Returned errors |
|---|---|---|---|---|
| search_records | 0 | 0 / 6 | 0% | 0 |
| get_record | 0 | 0 / 6 | 0% | 0 |
| update_record | 0 | 0 / 6 | 0% | 0 |
| export_records | 0 | 0 / 6 | 0% | 0 |
Use across agents
Each illustrated agent ran the same prompts with two repeats.
| Agent | MCP use rate | Used / runs | Tool calls | Returned errors |
|---|---|---|---|---|
| General assistant | 0% | 0 / 2 | 0 | 0 |
| Reasoning assistant | 0% | 0 / 2 | 0 | 0 |
| Fast assistant | 0% | 0 / 2 | 0 | 0 |
Run cohorts are independent of production call volume. Tool invocation does not prove task success.