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

# MCP tool reference

> The Tempo tools available to connected AI agents and assistants.

Tempo exposes self-describing MCP tools for deal context, seller workflows, and permitted configuration. Your client discovers each tool's current input schema when it connects.

The tools you see depend on your permissions and the capabilities available to your organization. You may see fewer tools than this reference lists.

## Toolsets

Tempo groups public MCP tools by job. The standard connection exposes the full public surface. If your MCP client accepts a custom server URL, add `?toolset=seller_default` for daily seller work without Build tools.

Use `?toolset=build` or include `build` in a comma-separated `toolset` value when an agent needs to configure Canvas, Skills, Signals, Automations, or Playbook sources. Build tools still enforce the same permissions as Tempo.

Older toolset names continue to resolve where possible: `planning` maps to Workspace, `memory` maps to Context, and `deal-ops` maps to CRM.

<Note>
  Provider connections, credentials, organization membership, and organization settings remain managed in Tempo.
</Note>

## Core

| Tool                  | Purpose                                                                    |
| --------------------- | -------------------------------------------------------------------------- |
| `get_session_context` | Get the signed-in user's organization, permissions, and available context. |
| `get_next_actions`    | Recommend the next actions for the user's current deal scope.              |
| `manage_profile`      | Update the signed-in user's first name, last name, or timezone.            |

The `get_started` prompt is always available and uses Core tools to help a seller choose a starting action.

## Workspace

| Tool                    | Purpose                                               |
| ----------------------- | ----------------------------------------------------- |
| `list_deals`            | Find deals the signed-in user can access.             |
| `get_deal_state`        | Get the current state and cited context for one deal. |
| `list_meetings`         | List meetings associated with accessible deals.       |
| `generate_canvas`       | Generate a published Canvas or selected draft blocks. |
| `get_canvas_generation` | Retrieve the result of a handed-off Canvas run.       |
| `list_action_items`     | List tasks.                                           |
| `get_action_item`       | Get one task.                                         |
| `manage_action_items`   | Create, update, complete, or delete tasks.            |

## CRM

| Tool                | Purpose                                           |
| ------------------- | ------------------------------------------------- |
| `list_deal_updates` | List proposed CRM field updates.                  |
| `list_fields`       | List fields available in the current scope.       |
| `describe_fields`   | Get field meanings and supported values.          |
| `manage_fields`     | Perform permitted field-management actions.       |
| `list_crm_objects`  | List supported CRM objects available to the user. |
| `create_crm_object` | Create a supported CRM object when permitted.     |

## Writing and communication

| Tool                   | Purpose                                    |
| ---------------------- | ------------------------------------------ |
| `get_writing_tone`     | Get the signed-in user's tone profile.     |
| `list_draft_messages`  | List draft messages.                       |
| `get_draft_message`    | Get one draft message.                     |
| `manage_draft_message` | Create, update, or manage a draft message. |

## Search, artifacts, and context

| Tool                     | Purpose                                                                                                   |
| ------------------------ | --------------------------------------------------------------------------------------------------------- |
| `search_deal_context`    | Search accessible deal context.                                                                           |
| `search_playbook`        | Answer questions from approved company Playbook guidance.                                                 |
| `list_artifacts`         | List accessible artifacts.                                                                                |
| `get_artifact`           | Get one artifact and its available content.                                                               |
| `write_artifact`         | Add artifact content to a deal.                                                                           |
| `manage_artifacts`       | Perform permitted artifact-management actions.                                                            |
| `list_context_sources`   | Inspect already-connected meetings, Notion pages, Slack channels, and contact or domain links for a deal. |
| `manage_context_sources` | Link or unlink already-connected evidence sources for a deal.                                             |

Context Sources manage which evidence belongs to a deal. They do not connect providers or handle credentials.

## Build

| Tool                      | Purpose                                                            |
| ------------------------- | ------------------------------------------------------------------ |
| `list_playbook_sources`   | List Playbook artifacts and their status.                          |
| `manage_playbook_sources` | Add or manage Playbook artifacts when permitted.                   |
| `list_automations`        | List Automations, run history, and readiness.                      |
| `manage_automations`      | Create or manage Automations when permitted.                       |
| `list_signals`            | List Signals.                                                      |
| `generate_signal`         | Draft a Signal from a plain-language request.                      |
| `generate_signal_preview` | Preview a Signal against existing context without saving results.  |
| `manage_signals`          | Create or manage Signals when permitted.                           |
| `list_canvas_templates`   | List Canvas templates. Pass `include_blocks=true` for block IDs.   |
| `manage_canvas_templates` | Create or manage Canvas templates when permitted.                  |
| `list_skills`             | Browse visible Skills or inspect one draft in detail.              |
| `use_skill`               | Activate a published Skill and return its instructions.            |
| `manage_skills`           | Create, update, publish, or delete Skills when permitted.          |
| `get_instance_setup`      | Inspect the configuration actions available to the signed-in user. |

Build tools enforce the same access rules as the web app. An unavailable action is not evidence that the underlying data is empty.

## Canvas generation

The `generate_canvas` and `get_canvas_generation` tools run Canvas generation. See [Build on Canvas with MCP](/canvas/developers/mcp) for the workflow.

### Refine a draft block by block

An agent can iterate on one section of a draft instead of re-running the whole template:

| Step                      | Call                                                       |
| ------------------------- | ---------------------------------------------------------- |
| Discover block IDs        | `list_canvas_templates` with `include_blocks=true`         |
| Edit the draft            | `manage_canvas_templates`, passing the revision you expect |
| Test selected sections    | `generate_canvas` with `block_ids`                         |
| Run the finished template | `generate_canvas` with `block_ids` omitted                 |

Block IDs are stable, so an agent can hold one across several edit-and-test rounds. `manage_canvas_templates` is revision-guarded: pass the revision you read, and a concurrent edit rejects your write instead of overwriting it.

These configuration tools are in the `build` MCP toolset.

## Use the live schema

Tool descriptions summarize purpose, not every parameter or response field. Use the schema returned by your MCP client as the contract for the connected environment.

<Note>
  Organization membership, teams, integration connections, provider mappings, API keys, and organization settings remain web-app administration tasks.
</Note>