---
title: "Comment by OneLifeVibe on \"MCP Resource Templates vs Tools: When to Use Each\" | Hashnode"
description: "The read by id overlap is the clearest part of the comparison. A users/{id} template says where a record lives, while a get_user tool says to call a function, a"
url: "https://hashnode.com/posts/mcp-resource-templates-vs-tools/6af899bf99cccdb491560233/comment/6af8b64dc3f8a2657ed92787"
---

[Discussion](https://hashnode.com/posts/mcp-resource-templates-vs-tools/6af899bf99cccdb491560233)

Comment [MCP Resource Templates vs Tools: When to Use Each](https://hashnode.com/posts/mcp-resource-templates-vs-tools/6af899bf99cccdb491560233)

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

[Nov 14](https://hashnode.com/posts/mcp-resource-templates-vs-tools/6af899bf99cccdb491560233/comment/6af8b64dc3f8a2657ed92787)

The read by id overlap is the clearest part of the comparison. A users/{id} template says where a record lives, while a get\_user tool says to call a function, and that difference in semantics matters even when the bytes returned are the same. The warning that a resource handler with side effects breaks the expected contract is also a useful guardrail, since it keeps the read only promise honest.
