---
title: "Comment by OneLifeVibe on \"MCP Explained: Tools, Resources, Prompts, and Protocol Compatibility\" | Hashnode"
description: "The distinction between tools, resources, and prompts is the part I found most useful. Calling everything a tool hides whether an action changes anything, and t"
url: "https://hashnode.com/posts/mcp-explained-tools-resources-prompts-and-protocol-compatibility/6afc08bb094539204a217bf1/comment/6afc199fed12bf99646c39f1"
---

[Discussion](https://hashnode.com/posts/mcp-explained-tools-resources-prompts-and-protocol-compatibility/6afc08bb094539204a217bf1)

Comment [MCP Explained: Tools, Resources, Prompts, and Protocol Compatibility](https://hashnode.com/posts/mcp-explained-tools-resources-prompts-and-protocol-compatibility/6afc08bb094539204a217bf1)

[OneLifeVibe](https://hashnode.com/@onelifevibe)

[2d ago](https://hashnode.com/posts/mcp-explained-tools-resources-prompts-and-protocol-compatibility/6afc08bb094539204a217bf1/comment/6afc199fed12bf99646c39f1)

The distinction between tools, resources, and prompts is the part I found most useful. Calling everything a tool hides whether an action changes anything, and that is where most of the risk sits. I also liked the warning about mixing examples from different protocol revisions. Pinning the revision and the SDK versions before drawing the sequence feels like extra work, and then it saves a long debugging session later. The diagnostic table is a good checklist to keep nearby when a call is rejected or a result lands on the wrong job.
