Problems / Agents and tools, medium
Agents repeat the same read-only lookups, but the tool-result cache hits 10% because it is keyed on raw arguments with timestamps.
Free to open. Runs in your browser, no sign-up.
Success ≥ 95% of tasks, p99 ≤ 90 s.
6 requests a second for 45 seconds: 100% task (writes).
What each component does in this design, and what calls it. The simulator mimics each one from these settings.
| Component | Its job here | Settings |
|---|---|---|
| Load balancerLoad balancer | Traffic enters here.Calls Agent API.Layer 4 balancers route by IP and port; layer 7 balancers read HTTP and can route by path or header. | – |
| Agent APIApp service | Load balancer forwards to it.Calls Agent orchestrator.Little's law: throughput ≈ concurrency ÷ latency. 200 slots at 50 ms serve about 4,000 req/s. | 3 replicas × 500 slots · timeout 180 s |
| Agent orchestratorAgent orchestrator | Agent API calls it.Calls Model, Tool result cache.An agent loops: think, call a tool, read the result, repeat until done. | 400 slots · 6 steps |
| ModelLLM endpoint | Agent orchestrator calls it.Latency has two parts: time to the first token, then a steady stream of tokens per second. | 300 streams |
| Tool result cacheTool result cache | Agent orchestrator calls it.Calls MCP tool servers.Agents often repeat the same read-only tool call within and across tasks. | 5000 slots · 10% hit rate |
| MCP tool serversTool / MCP server | Tool result cache calls it.Tools give the model actions such as search or database queries; each call is another round trip. | 8 slots |
Try it first. Open one hint at a time if you get stuck.
Every miss goes to the slow tool.
Normalise cache keys for read-only tools.
Raise the tool-result cache hit rate.