Research notebook

Selective tool calls: finding the cost threshold notebook

Edit a Python cell and run it here. Your code runs in this browser tab; the notebook runtime and packages are served by this site.

Python starts when you choose Run.

Selective tool calls: finding the cost threshold

A carry-detection fixture makes the error–latency trade-off explicit, including the point at which a perfect calculator stops being worthwhile.

Synthetic routing utility calculation; no learned Toolformer, model confidence, or measured tool latency.

Python · cell 1
n_tasks 50 latency is simulated, not measured
ms=0 threshold=0 calls=50 errors=0 objective=0.020
ms=0 threshold=8 calls=20 errors=0 objective=0.008
ms=0 threshold=10 calls=10 errors=0 objective=0.004
ms=0 threshold=12 calls=3 errors=7 objective=0.141
ms=0 threshold=15 calls=0 errors=10 objective=0.200
ms=250 threshold=0 calls=50 errors=0 objective=0.070
ms=250 threshold=8 calls=20 errors=0 objective=0.028
ms=250 threshold=10 calls=10 errors=0 objective=0.014
ms=250 threshold=12 calls=3 errors=7 objective=0.144
ms=250 threshold=15 calls=0 errors=10 objective=0.200
ms=5000 threshold=0 calls=50 errors=0 objective=1.020
ms=5000 threshold=8 calls=20 errors=0 objective=0.408
ms=5000 threshold=10 calls=10 errors=0 objective=0.204
ms=5000 threshold=12 calls=3 errors=7 objective=0.201
ms=5000 threshold=15 calls=0 errors=10 objective=0.200
Threshold 10 / never-call indifference: 4900 simulated ms
Python · cell 2

Python runs locally in this page. Saved results and figures are visible before execution.

Download full experiment notebook