Same agent, same faults, two ways to see the cluster. The one with the resource graph and change timeline used 76% fewer tool calls and finished in half the time.
We benchmarked an AI agent on 52 broken clusters: kubectl vs a Kubernetes MCP server
Related
Building a Multi Agent Townhall simulation from scratch
I wanted to understand how multi-agent systems actually work — not from a tutorial, but by wiring the...
Your AI Coding Assistant Has No Memory of Why
A pull request lands. Two approvals, tests green, CI blue. It ships on a Tuesday. Three weeks later...
How I Fixed Hallucinations by Switching from AGENTS.md to AGENTS.db
Before I dive in, a bit of background on how our agentic workflow at Exam Intelligence for deep...