zlacker

[parent] [thread] 5 comments
1. tarasy+(OP)[view] [source] 2026-02-04 10:24:32
Simple question: why not a cli instead? As seems that lately LLM and agentic tools seems to be better at using clis rather than bloated MCPs?
replies(4): >>NicuCa+Z >>stingr+o5 >>esafak+By >>somniu+lH
2. NicuCa+Z[view] [source] 2026-02-04 10:32:56
>>tarasy+(OP)
I think they're only better for CLI tools that are in the training data. If it's a new tool, you'd need to dump the full documentation in the context either way.
replies(1): >>occz+eE
3. stingr+o5[view] [source] 2026-02-04 11:06:29
>>tarasy+(OP)
This is what I was thinking, or fewer, more versatile tools. Having the description of 110 tools in your context window at all times is just noise.
4. esafak+By[view] [source] 2026-02-04 14:23:46
>>tarasy+(OP)
Because it was started before the revelation MCP was a context hog. https://github.com/LaurieWired/GhidraMCP
◧◩
5. occz+eE[view] [source] [discussion] 2026-02-04 14:52:18
>>NicuCa+Z
This can be solved well enough by having the model invoke `--help`
6. somniu+lH[view] [source] 2026-02-04 15:05:42
>>tarasy+(OP)
Tools like Claude Code have improved here. They won’t load all tools but instead rely on tool search. Context bloat of MCP servers was a thing if badly written clients but it’s certainly getting better
[go to top]