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

# Tools Overview

> Tools are the capabilities you enable for Neo Agents to accomplish tasks

Tools define what actions Neo Agents can perform. When you configure a workflow, you select which tools are available and customize their settings to match your processes.

<Info>
  Some tools turn on **automatically** once you configure an integration's permissions on the workflow's **Integrations** tab — the PSA, RMM, Microsoft 365, IT Glue, and Hudu API tools all work this way. You pick which permission groups the agent can use; the matching tool appears without a separate toggle.
</Info>

## Tool Categories

<CardGroup cols={2}>
  <Card title="PSA" icon="ticket" href="/agents/tools/psa/psa-api">
    Read and write your PSA — tickets, notes, time entries, contacts, configurations, and more
  </Card>

  <Card title="RMM" icon="server" href="/agents/tools/rmm/run-rmm-script">
    Read device and monitoring data, and run scripts on target devices to fix problems
  </Card>

  <Card title="Microsoft 365" icon="microsoft" href="/agents/tools/m365/overview">
    Manage Entra ID, Active Directory, Exchange, and Intune — users, groups, licenses, mailboxes
  </Card>

  <Card title="Communication" icon="comments" href="/agents/tools/communication/add-client-facing-note">
    Send messages to end users and internal teams — ticket notes, email, Teams, SMS
  </Card>

  <Card title="Search" icon="magnifying-glass" href="/agents/tools/search/find-documentation">
    Find documentation, similar tickets, configurations, and web resources
  </Card>

  <Card title="Documentation" icon="book" href="/agents/tools/documentation/itglue-api">
    Read and write IT Glue and Hudu documentation, configurations, and assets
  </Card>

  <Card title="Management" icon="list-check" href="/agents/tools/management/external-api-request">
    Log time, generate passwords and secure links, trigger workflows, call external APIs and Neo's own API
  </Card>

  <Card title="Built-in & Internal" icon="gear" href="/agents/tools/built-in/overview">
    Tools the agent always has or gets automatically — search helpers, the sandbox, plumbing
  </Card>

  <Card title="Approvals" icon="user-check" href="/agents/tools/approvals/request-technician-approval">
    Request human approval before sensitive actions
  </Card>
</CardGroup>

## Credit Tiers

Each tool is assigned a credit tier based on its complexity. Your workflow's credit cost is determined by the highest-tier tool enabled.

| Tier                                                | Cost      | Description                                                                        |
| --------------------------------------------------- | --------- | ---------------------------------------------------------------------------------- |
| <Icon icon="circle" color="#22c55e" /> **Basic**    | 1 credit  | Simple operations — retrieving data, generating passwords                          |
| <Icon icon="circle" color="#eab308" /> **Standard** | 2 credits | Documentation search, ticket search, sandbox shell                                 |
| <Icon icon="circle" color="#ef4444" /> **Advanced** | 3 credits | PSA API writes, RMM script execution, Microsoft 365 operations, external API calls |

<Note>
  For the API-backed integration tools (PSA, RMM, IT Glue, Hudu), the effective tier reflects the access you grant — Standard when every enabled permission group is Read Only, Advanced when any group allows writes.
</Note>

## Tool Dependencies

Some tools automatically enable other tools they depend on. For example:

* **Execute RMM Script** automatically enables the device-lookup and script-search capabilities it needs
* Update and create operations automatically enable the field-options lookups they need

<Info>
  Dependency tools are shown in each tool's documentation. They're automatically enabled when you select the parent tool.
</Info>

## Technician-in-the-Loop

Many tools support **Technician-in-the-Loop** approval, which requires human approval before the agent takes action. When enabled:

1. The agent prepares the action and explains what it wants to do
2. A Teams message is sent to configured technicians
3. A technician approves or rejects the action
4. The agent proceeds based on the decision

<Tip>
  Start with approval enabled for sensitive operations. As you gain confidence in the agent's decisions, you can disable approval for routine tasks.
</Tip>
