# Find available tools

List a source’s methods, inspect the one you need, and use its exact input schema.

Use tool discovery when you know the source or task but do not know which operation to call. Discovery does not run the listed methods. You can inspect capabilities before performing a read or write.

## Discover and inspect an operation

1. **Find the source**

   ```sh
   zortex manage --json '{"what":"sources"}'
   ```

   Locate the exact source ID, such as `gmail`, `google-drive`, `browser-use`, or `cua`. Inspect its state. An unavailable or disabled source may need [setup or recovery](/docs/vision/connectors/recovery) before it can execute anything.

   For shared actions that are not specific to an app, run `zortex actions` without a source. That list gives names. Use `zortex instruction` and the [Action reference](/docs/vision/reference/actions) for fixed inputs such as sharing; do not assume every shared action has a source-specific schema lookup.

2. **List its methods**

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

   Read the names and descriptions in the returned catalog. Choose the method that matches the intended operation and effect. Do not construct a method name from an app name.

   Some catalogs accept `query`, `resource`, `limit`, `cursor`, or `profile`. Follow the installed tool and catalog's returned pagination information. Filtering one source's catalog is not a search of your messages or documents, and one page is not necessarily the whole catalog.

3. **Inspect the selected schema**

   Replace the placeholder with the exact method returned in step 2:

   ```sh
   zortex actions --json '{"source":"gmail","method":"<returned-method-name>"}'
   ```

   Check the required fields, accepted values, account/resource selectors, effect, and response description. If an operation changes data, verify that its target and scope match your task before invoking it. A readable schema does not prove the account has permission to execute it.

   Sources with a shared bounded-read route can expose the schema for `connector.read`:

   ```sh
   zortex actions --json '{"source":"gmail","method":"connector.read"}'
   ```

   If that source does not offer it, use the method its actual catalog returned. Browser actions have their own fixed names and are invoked directly; provider and computer methods normally use `connector.invoke`.

4. **Run the operation**

   Continue with [Run an action](/docs/vision/tools/actions). It explains the shared read path, provider invocation, result checks, and write recovery.

   **MCP equivalents**

   ```text
   indra.manage({"what":"sources"})
   indra.actions({"source":"gmail"})
   indra.actions({"source":"gmail","method":"<returned-method-name>"})
   ```

   These are tool requests made by a connected agent, not terminal commands. [MCP tool reference](/docs/vision/reference/mcp-tools) lists their arguments.

## When discovery fails

| Symptom | What to check |
| --- | --- |
| Source is missing | Confirm the source ID and installed source inventory. Do not infer support from another installation. |
| Source is disabled | Preserve the setting unless enabling it is intended; see [Permissions](/docs/vision/settings/permissions). |
| Catalog is empty | Check whether the source offers a shared read route or needs setup. Empty catalog is not a successful task. |
| Method was listed but schema lookup fails | Refresh the current catalog and use the exact name from the same source/profile. |
| Schema works but invocation fails | Read the operation error; connection, resource permissions, or required arguments can still be missing. |

You are ready to act when you have the current method name, its schema, the intended source/account, and the required input values.
