Model Context Protocol · Free worked guide
MCP Tools vs Resources: When to Use Each
Choose between MCP tools and resources by intent, side effects, discovery, user control, and the evidence your workflow needs.
By ClaudeQuest · Reviewed · Independent learning material
What is the difference between MCP tools and resources?
Resources expose context that an application can read; tools represent callable operations. The boundary matters because actions, especially side effects, need stronger validation, permission, and recovery controls.
Decision rule: Model information as a resource and an operation as a tool; never hide a state change behind a read-like name.
Use it in a real situation
An integration can show a deployment status to an engineer or initiate a production deployment with customer impact.
- Name the observable outcome and the constraint that changes the decision.
- Choose the smallest action that can produce useful evidence.
- Keep permissions, uncertainty, and side effects visible before execution.
- Run a check that could disprove the approach, then record what remains unknown.
Original ClaudeQuest worked example
From vague request to reviewable result
Task or input
Expose status as a resource or read operation. Make deployment a separately named tool with environment, version, approval, and idempotency inputs.
Better result
The model and user can distinguish observation from mutation before authority is granted.
How to verify it
Confirm the read path cannot mutate, the tool declares side effects, and retries cannot create duplicate actions.
Three mistakes to avoid
Copying without adaptation. Replace repository, data, user, and authority assumptions with facts from your environment.
Treating prose as enforcement. Use permissions, validation, tests, and human approval for boundaries that must hold.
Calling one success proof. Re-test the decision with a different input or context before treating it as a durable skill.
Related Model Context Protocol guides
Source and scope
Primary technical reference: Model Context Protocol concepts. Source reviewed September 13, 2026. Product capabilities can change; verify time-sensitive details against the current primary documentation.
The scenario and worked example are original ClaudeQuest learning material. ClaudeQuest is independent of Anthropic and does not guarantee tool performance, certification results, or professional outcomes.
Read the editorial and evidence method →