# Resources

> The two resource URIs — a task and a saved view — and when a client should read one instead of calling a tool.

**What this is:** things a client can read as context, by URI. **When you need it:** attaching a particular task or saved view to a conversation.

| URI | Is | Scope | Same as |
| --- | --- | --- | --- |
| `tasksmate://task/{id}` | One task. | `tasks:read` | [`tasks.read`](https://developers.tasksmate.indrasol.com/reference/operations/tasksread/) |
| `tasksmate://view/{id}` | One saved view. | `tasks:read` | [`views.read`](https://developers.tasksmate.indrasol.com/reference/operations/viewsread/) |

finalised at 5.1: What each resource returns — its content and MIME type.

## Read, or call a tool?

-   **Read a resource** when you already know which task or view you mean and want it in front of the model — for example, attaching `tasksmate://task/T123456` to the chat before asking about it.
-   **Call a tool** when the model has to find, filter or change something: `search_tasks`, `list_my_tasks`, `update_task`.

Resources are read-only; everything that changes data is a [tool](https://developers.tasksmate.indrasol.com/mcp/tools/). Reading one needs the same scope as the API read behind it, and sees only what your access sees there.

---
Source: https://developers.tasksmate.indrasol.com/mcp/resources/