When you build MCP servers you must've noticed your agent makes more tool calls than it should or gets stuck halfway "even" when you gave it every tool it needs. The problem is not the server, it's the way we design it. Most of us build MCP servers like we build APIs: expose endpoints as tools and let the agent figure out the rest. Exactly the "figuring out" part is the problem.

We're handing agents too many planning responsibility instead of giving them exact intent. We'll test the idea by building same workflow in 2 different ways and you will see see how a simple chnange in our design made one process leading to unnecessary planning or tool calls while other is more effortless .

You'll leave knowing how to design from the agent's perspective instead of the developer's so next time you're deciding what tools to expose and how much abstraction your server needs, the answer is obvious instead of a guess. And hopefully you can make your agent's life easier (work smarter, not harder!!!) :)