# Overview

Understand tool discovery, typed inputs and results, approval boundaries, failure reporting, and the difference between built-in, plugin, and MCP tools.

![Tools in Foxora v5.0.3](/docs/images/v5.0.3/studio/tools-overview.webp)

## Where this lives

Open **studio → Tools**.

Tools are typed capabilities that let an agent inspect or change files, run commands, browse, control applications, query services, or call connected integrations.

> **Safety:** Tool output is untrusted data and can contain misleading instructions. Do not grant a tool broader filesystem, account, or network access merely to avoid configuration work.

## Steps

1. Open **studio → Tools**.
2. Understand tool discovery, typed inputs and results, approval boundaries, failure reporting, and the difference between built-in, plugin, and MCP tools.
3. Search the built-in tool catalog by capability, inspect the tool’s expected inputs and permission boundary, then enable it only through the agent, skill, or workflow that needs it.
4. **Confirm the result.** Run one representative call, inspect the structured result or error, and confirm the underlying file, process, page, application, or external service changed as intended.

## Choose the right path

- Use built-in tools for local and first-party capabilities.
- Use Composio-managed plugins for supported SaaS integrations.
- Use MCP for a custom or organization-provided tool server.


## Confirm it worked

- Run one representative call, inspect the structured result or error, and confirm the underlying file, process, page, application, or external service changed as intended.
- The screen, command, file, run, or destination named in this guide reflects the expected state.