It was initially a huge context slob, but now that most harnesses support tool-discovery and MCP 2.0 decided on a senseful stateless API i can accept it.
yeah good luck reliably teaching your agent how to use a novel REST api, esp a REST api that is niche or doesn't really exist publicly. it's far more natural for it to be a tool call available to it.
i have an mcp that hosts a clangd server plus a skill to use it to perform LSP queries against a codebase
that allows for the language server to persist across calls
yea idk if there’s any that work in the terminal? hmm
in web ui chats they are v cool
map and calendar are basic examples where me n my agent can get on the same page much better than via prose, you can imagine others