# Using tools

Find saved information, read current app data, and take actions through the terminal or your agent.

Tools let you work with your apps and local information. Start by choosing whether the task needs saved context, current service data, or an interactive interface. Then use the guide for that path.

## Try a tool

### Terminal

On an installed system, list the shared actions:

```sh
zortex actions
```

To inspect one source's available methods:

```sh
zortex actions --json '{"source":"gmail"}'
```

### Agent host

With an agent host connected through MCP, the equivalent requests are:

```text
indra.actions({})
indra.actions({"source":"gmail"})
```

A catalog is a list of operations, not their results. [Find available tools](/docs/vision/tools/discovery) shows how to inspect a method's required fields and execute it. For a complete first read, follow [Get started](/docs/vision/quickstart).

## Choose the right capability

### [Search saved information](/docs/vision/tools/search)

Information already collected from several sources. Read-only SQL over the local Vault.

### [Read live data and verify sources](/docs/vision/tools/read)

Current information from a connected app. A source read.

### [Run an action](/docs/vision/tools/actions)

A change in a connected app. The source's action method.

### [Work with local files](/docs/vision/tools/local-files)

A file in an allowed folder. The local file connector.

### [Use a browser](/docs/vision/browser-computer/browser-use)

Interaction with a website. A browser session and current page controls.

### [Use your computer](/docs/vision/browser-computer/computer-use)

Interaction with a desktop application. The installed computer provider.

### [Save and share results](/docs/vision/tools/sharing)

A saved output or static handoff. A file or selected share snapshot.

Use a connected action when it can do the job directly. For example, read a document through its service operation before navigating the same document through a browser. Use an interface when it provides the necessary capability or the task is specifically about that interface.

## Saved information and current information

A search of the Vault answers questions about collected records. A connector read asks the provider now. A source can have useful live actions without an imported history, and old records can remain after a connection stops working.

Choose a live read when the latest state matters. Choose saved search when you need collected context across sources. If local search is empty, check [coverage](/docs/vision/connectors/coverage) before concluding the information does not exist. Do not start a full import just to perform one supported live action.

## Discovery, skills, and longer work

Vision discovers source methods through `actions`, with filtering and pagination where the source supports them. The [source catalog](/docs/vision/tools/discovery) describes the available methods and their exact arguments.

Skills in your agent host can teach that agent a workflow, but they do not create an additional Vision action or grant new access. Longer operations use their own returned job or session state. See [Follow long-running work](/docs/vision/autopilot/long-running-tasks); there is no generic asynchronous tool or universal task queue to invoke by guessing a name.

## Finish with a checked result

For information, open the relevant records and keep their source identities. For a change, read the resulting object or inspect the page where the effect should appear. For a pending job, keep its returned identity and continue the same work. [Read live data and verify sources](/docs/vision/tools/read) and [Run an action](/docs/vision/tools/actions) show these checks in detail.
