Your MCP Doesn't Need 30 Tools: It Needs Code
Briefly

CLI tools are often platform-dependent and version-specific, causing failures during initial use. Issues arise particularly with non-ASCII string inputs, where tools like Sonnet and Opus encounter difficulties. Agentic coding tools experience challenges when handling specific syntax, such as appending newlines. Additionally, tools like Claude Code implement security checks that add delays before executing commands. These multi-turn operations complicate interactions with CLI tools. A suggested alternative is utilizing MCP servers that provide a simplified interface for accepting programming code as tool inputs, which could mitigate some challenges associated with traditional CLI tools.
CLI tools can present challenges due to their platform and version dependency, leading to inconsistent performance and failures, especially regarding non-ASCII string inputs.
Agentic coding tools often struggle with tool usage that requires specific syntax, particularly with trailing newlines and how to manipulate them in a file.
The security preflight check in certain agentic tools, such as Claude Code, adds latency to tool execution, complicating multi-turn interactions.
Using MCP servers to expose single tools that accept programming code as inputs offers a potential solution to some of the limitations of CLI tools.
Read at Armin Ronacher's Thoughts and Writings
[
|
]