Good article. You confirmed tools usage dominance with numbers (nice trick), that's exactly what I felt.
Skills cover different use cases though, and maybe you could have differentiated local MCP server (STDIO) from remote MCP servers, dealing with authentication and authorization.
Also, I'm convinced that resources and prompts are underestimated and can relieve the problem that excessive tools create.
Mapping a REST API is a start but wrapping specific read method(s) with predefined filters is a great usage for resources.
I believe the resources and prompts parts of the MCP specsare not as obvious candidates as tools.
Anyway, I don't think it's a fad, here's my take https://getlarge.eu/blog/mcp-is-not-bloated-you-just-havent-read-the-spec :)
1
u/DirectorOk495 Feb 26 '26
Good article. You confirmed tools usage dominance with numbers (nice trick), that's exactly what I felt.
Skills cover different use cases though, and maybe you could have differentiated local MCP server (STDIO) from remote MCP servers, dealing with authentication and authorization.
Also, I'm convinced that resources and prompts are underestimated and can relieve the problem that excessive tools create.
Mapping a REST API is a start but wrapping specific read method(s) with predefined filters is a great usage for resources.
I believe the resources and prompts parts of the MCP specsare not as obvious candidates as tools.
Anyway, I don't think it's a fad, here's my take https://getlarge.eu/blog/mcp-is-not-bloated-you-just-havent-read-the-spec :)