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

# Resources & Prompts

> Beyond tools, the SmartAlex MCP server ships 7 ambient-context resources and 5 ready-made workflow prompts your AI client can use out of the box.

Tools are the actions an AI client can take. **Resources** and **prompts** are the other two halves of MCP: resources give the client ambient context about your workspace, and prompts are pre-built workflows it can run on request.

## Resources (7)

Resources are read-only context the client can pull in without calling a tool. An AI client that supports MCP resources can load these to understand your workspace before it does anything.

| Resource              | URI                            | What it gives the client                                      |
| --------------------- | ------------------------------ | ------------------------------------------------------------- |
| **Platform status**   | `smartalex://platform/status`  | Platform health and usage stats                               |
| **Agents**            | `smartalex://agents`           | All voice agents for your workspace                           |
| **Active campaigns**  | `smartalex://campaigns/active` | Every campaign with status, mode, and agent assignment        |
| **Recent calls**      | `smartalex://calls/recent`     | The most recent 25 call records                               |
| **Deals pipeline**    | `smartalex://deals/pipeline`   | All deals with stage, value, and contact                      |
| **Workflows**         | `smartalex://workflows`        | Recommended multi-step workflows, how to chain tools together |
| **Contacts overview** | `smartalex://contacts/stats`   | The first 25 contacts for a quick overview                    |

<Note>
  The **Workflows** resource is worth loading first. It tells the client how to chain SmartAlex tools into common jobs (qualify a lead, run a campaign, review the pipeline) so it plans multi-step work correctly.
</Note>

## Prompts (5)

Prompts are ready-made workflow templates. In clients that surface MCP prompts (as slash commands or a prompt picker), these appear as one-click starting points, each already wired to the right tools and resources.

| Prompt                 | Arguments                                       | What it does                                           |
| ---------------------- | ----------------------------------------------- | ------------------------------------------------------ |
| **Campaign strategy**  | `goal` (required), `target_audience` (optional) | Design an outbound campaign strategy                   |
| **Lead qualification** | none                                            | Review contacts and call history to qualify leads      |
| **Agent design**       | none                                            | Review your voice agents and suggest improvements      |
| **Call analysis**      | `focus` (optional)                              | Deep analysis of recent calls with actionable insights |
| **Pipeline review**    | none                                            | Review the deals pipeline with recommendations         |

## Using them together

A typical session leans on all three:

```mermaid theme={null}
flowchart LR
    R["Resources<br/>ambient context"] --> P["Prompt<br/>e.g. Pipeline review"]
    P --> T["Tools<br/>list_deals, update_deal"]
    T --> Out(["Recommendations + updates"])
```

The client loads **resources** to understand your workspace, you kick off a **prompt** to frame the task, and the prompt drives the **tools** that read and change your data.

<CardGroup cols={2}>
  <Card title="Tools reference" href="/mcp/tools-reference">
    Every one of the 28 tools, by domain.
  </Card>

  <Card title="Worked examples" href="/mcp/examples">
    Real prompts and the tool chains they trigger.
  </Card>
</CardGroup>