Intermediate
Open
Pro
Why Tools, Resources and Prompts Aren't Interchangeable
A junior engineer designing an MCP server for an internal wiki
proposes exposing everything as a single tool: wiki_action(action, args), where action can be "read_page", "search", or
"edit_page".
- Using the tools/resources/prompts distinction, explain what's wrong with this design.
- Propose a better shape for the same underlying capability.
- Why does this distinction matter more for security than for pure usability?
Share this question