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

# Available Tools

> Everything your AI assistant can do in Exec, what it reads or changes, and an example prompt for each.

**You do not need to read this to use Exec through an assistant.** Ask in plain language and it works out which capability to use. This page exists for the reader who wants to know exactly where the edges are, which is usually somebody doing a review.

Everything below is subject to your own Exec permissions. Having a capability listed here does not mean you can use it on data you cannot otherwise see. See [What the AI can see](/mcp/what-the-ai-can-see).

***

## Reading your workspace

| Capability        | Reads or changes | Example prompt                                            |
| :---------------- | :--------------- | :-------------------------------------------------------- |
| Workspace details | Reads            | `Which Exec workspace am I connected to?`                 |
| People            | Reads            | `Who is in my workspace, and what are their roles?`       |
| Groups and teams  | Reads            | `What groups do we have and how many people are in each?` |
| Connection check  | Reads            | `Check my Exec connection is working.`                    |

***

## Practice and results

| Capability                          | Reads or changes | Example prompt                                                                               |
| :---------------------------------- | :--------------- | :------------------------------------------------------------------------------------------- |
| Search roleplay sessions            | Reads            | `Show me every roleplay session from the last two weeks, worst score first.`                 |
| One session in detail               | Reads            | `Walk me through session [id], including the transcript and per-criterion feedback.`         |
| Coach feedback across many sessions | Reads            | `Summarize the coach feedback across my team's last ten sessions and find the common theme.` |

<Tip>
  Ask for feedback across many sessions in one go rather than one at a time. It comes back in a single request, so ten sessions is about as fast as one. Save the full transcript for the one session you want to examine closely.
</Tip>

***

## Skills and scenarios

| Capability                        | Reads or changes | Example prompt                                                                                          |
| :-------------------------------- | :--------------- | :------------------------------------------------------------------------------------------------------ |
| Skill proficiency across the team | Reads            | `Which skill is my team weakest at, counting only skills with at least 20 people scored?`               |
| Skill proficiency per person      | Reads            | `How is [name] doing on objection handling?`                                                            |
| Scenario performance              | Reads            | `How is the team doing on the discovery call scenario? Include improvement from first to best attempt.` |

<Warning>
  These require workspace admin or group admin, including when a member asks only about their own scores. Their own sessions, grades, and coach feedback are still readable through the rows above.
</Warning>

***

## Assignments

| Capability                        | Reads or changes | Example prompt                                                         |
| :-------------------------------- | :--------------- | :--------------------------------------------------------------------- |
| List assignments and their status | Reads            | `Who has not finished the discovery assignment, and what is past due?` |

Status values are not started, in progress, completed, past due, and did not pass. Each row carries the due date, the best score and rank so far, and attempts against what was required.

***

## Building a roleplay

| Capability                            | Reads or changes                     | Example prompt                                                                             |
| :------------------------------------ | :----------------------------------- | :----------------------------------------------------------------------------------------- |
| Describe a scenario and have it built | **Changes**, creates a draft         | `Build me a cold call where the buyer is a skeptical CFO who thinks we are too expensive.` |
| Check on progress                     | Reads                                | (your assistant does this by itself while you wait)                                        |
| Stop it part way                      | **Changes**, stops the work          | `Stop building that scenario.`                                                             |
| Publish the draft                     | **Changes**, creates a live scenario | `Publish it, just for me.`                                                                 |

Building takes anywhere from under a minute to a few, and your assistant checks back on its own. It always describes the draft before publishing. Stopping part way keeps whatever was already written to the draft.

Publishing enforces your workspace's limit on custom scenarios, so if you are at your limit it will say so.

<Warning>
  Publishing shares the scenario with the whole workspace. To keep it to yourself, ask to set its visibility to you.
</Warning>

One quirk worth knowing: scenario requests are checked for content that reads as code or as instructions to the assistant, and those are rejected with a note asking you to rephrase. **If you paste a formatted scenario spec and it is refused, describe it in plain sentences instead.** That is the most common surprise in this whole feature.

***

## Charts and dashboards

| Capability                         | Reads or changes | Example prompt                                  |
| :--------------------------------- | :--------------- | :---------------------------------------------- |
| Render metrics, charts, and tables | Reads            | `Give me a dashboard of this month's practice.` |

Charts come out in Exec's colours and use Exec's vocabulary. They need an assistant that can display interactive panels. In a text-only assistant you get the numbers instead, and nothing breaks. See [Limits](/mcp/limits).

***

## Everything else in Exec

Courses, certifications, programs, and call scoring have no dedicated capability, but an assistant can still query them, so questions like `which courses has [name] completed?` generally work. Expect an extra step or two while it works out how to ask.

For call scoring specifically, what comes back is whatever **your** scorecards and call categories are configured to capture, not a fixed set of measures. A question about objection handling lands if objection handling is one of the things you score. If it comes back thin, ask in the language of your own criteria.

This path is read-only. Requests to change anything are rejected before they run.

**Knowledge Hub content is not reachable this way.** It can be used as source material when building a scenario, but it cannot be searched or read back to you.

***

## Next

<CardGroup cols={2}>
  <Card title="What the AI can see" href="/mcp/what-the-ai-can-see">
    Permissions, in full
  </Card>

  <Card title="Limits" href="/mcp/limits">
    Sizes, caps, and what to do about them
  </Card>
</CardGroup>
