An Agent Can't Offer an MCP Tool It Can't See
MCP discovery tells an agent how to authenticate, not what a tool does. When a tool sits behind per-user login, static metadata is the fix, not a smarter model.
I lead engineering teams.
Senior Engineering Manager at Staffbase — communities, mobile, and a plugin platform built for the agent era.
I ship with agents.
Specs, plans, reviews, phase gates — I manage AI agents the way I manage engineers.
I write about what that changes.
Agentic workflows, engineering leadership, and the craft in between.
Latest writing
All posts →-
-
Descope by Context, Not by Headcount
When your team is overloaded, don't descope by task count. Hand off the work that costs the least context to lose, not the biggest item on the board.
-
Put the Guardrail in the Code, Not the Prompt
Hard limits for AI agents belong in code, not the prompt: the model reads prompt rules and breaks them. Plus the deny-by-default trap that does nothing.
-
AI Finds the Issue. Then It Throws the Hot Potato.
AI made finding code issues free, but owning the fix still needs a human. Why finding throughput is a vanity metric and the hand-back is the real work.
-
Simplicity Is Invisible by Design. That Makes It a Management Problem.
Engineering teams reward complexity by accident because simplicity leaves no artifact. Four ways a manager can make avoided complexity visible.