---
title: "Discussion on \"MCP Resource Templates vs Tools: When to Use Each\" | Hashnode"
description: "Discussion on \"MCP Resource Templates vs Tools: When to Use Each\". Read data through resource templates, act through tools."
url: "https://hashnode.com/posts/mcp-resource-templates-vs-tools/6af899bf99cccdb491560233"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [MCP Resource Templates vs Tools: When to Use Each](https://blogs.powerduck.com/mcp-resource-templates-vs-tools?utm_source=hashnode&utm_medium=feed)

Read data through resource templates, act through tools.

Nov 14 · 5 min read · blogs.powerduck.com  
Read the article

-   [#ai](https://hashnode.com/tag/ai)
-   [#api](https://hashnode.com/tag/api)
-   [#tools](https://hashnode.com/tag/tools)
-   [#programming](https://hashnode.com/tag/programming)

## Written by

[Powerduck](https://hashnode.com/@powerduck)

@powerduck · hon

  
[View profile](https://hashnode.com/@powerduck)

## Responses 1

Markdown supported · ⌘↵ to post

[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.
