> ## Documentation Index
> Fetch the complete documentation index at: https://docs.cometly.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Resources Overview

> Subscribable read-only data the MCP server exposes alongside tools — workspace context, metric catalogs, dimension lists.

MCP **Resources** are read-only documents your client can subscribe to once and re-read on demand without burning tool-call budget. Cometly exposes five resources covering workspace orientation and the analytics vocabulary.

## At a glance

| URI                                    | Description                                                                                                                                   | Mime               |
| -------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------- | ------------------ |
| `cometly://workspace/context`          | Same payload as [`get_workspace_context`](/mcp/tools/get-workspace-context) — timezone, currency, connected ad accounts, custom event labels. | `application/json` |
| `cometly://catalog/metrics`            | Every supported analytics metric slug + category + label.                                                                                     | `text/csv`         |
| `cometly://catalog/attribution-models` | Every attribution model with a one-line description.                                                                                          | `application/json` |
| `cometly://catalog/dimensions`         | Every `group_by` dimension across analytics tools.                                                                                            | `application/json` |
| `cometly://catalog/custom-events`      | Live custom-event slot ↔ label map for this space.                                                                                            | `text/csv`         |

## When to use a Resource vs a tool

Resources are best for **static-ish reference data** the agent shouldn't re-fetch every turn:

* Metric catalogs change rarely — fetch once per session.
* Attribution model definitions never change.
* Dimension lists never change.
* Custom event labels change when the user re-labels a slot — re-fetch occasionally.

For dynamic data (current campaign performance, recent webhooks, etc.) use the corresponding tool.

## Subscribing

OAuth-aware clients (Claude Desktop, Cursor) handle Resource subscription automatically. Resource reads are subject to the same `mcp_space:{id}` ability as tools.

## Example — reading a Resource

The MCP `resources/read` method returns the resource body in the same format the corresponding tool would produce:

```json theme={null}
{
  "method": "resources/read",
  "params": {
    "uri": "cometly://catalog/custom-events"
  }
}
```

Response (truncated):

```csv theme={null}
slot,label,include_in_gross_revenue
custom_event_2,Deal Created,true
custom_event_5,Lead Magnet,false
```