Just to echo the point of MCP, they seem cool, but in my experience just using a CLI is orders of magnitude faster to write and to debug (I just run the CLI myself, put test in the code, etc...)

▲

jascha_eng a day ago | parent | next [-]

Jup and it doesn't bloat the context unnecessarily. The agent can call --help when it needs it. Just imagine a kubectl MCP with all the commands as individual tools, doesn't make any sense whatsoever.

	▲	nomel a day ago \| parent \| next [-]
		> and it doesn't bloat the context unnecessarily. And, this is why I usually use simple system prompts/direct chat for "heavy" problems/development that require reasoning. The context bloat is getting pretty nutty, and is definitely detrimental to performance.
	▲	okeuro49 a day ago \| parent \| prev [-]
		Do you have any information e.g. blog posts on this pattern?

▲

HDThoreaun a day ago | parent | prev [-]

The point of this stuff is to increase reliability. Sure the LLM has a good chance of figuring out the skill by itself, the idea is that its less likely to fuck up with the skill though. This is an engineering advancement that makes it easier for businesses to rely on LLMs for routine stuff with less oversight.