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

# Agent Tools

> Use Fleet agent tools in Ravenna rules to look up devices, check health status, and run osquery diagnostics during automated ticket handling.

Fleet provides AI agent tools for device management, health monitoring, and diagnostic workflows. Reference these tools in <Tooltip headline="Agent rules" tip="Natural language instructions defining agent behavior" cta="Learn about agent rules" href="/documentation/automate/agents/configure#rules">agent rules</Tooltip> using @ mentions to enable automated device troubleshooting and information retrieval.

***

## Available tools

<AccordionGroup>
  <Accordion title="Look up device" defaultOpen>
    Retrieves device information for a user including hostname, serial number, platform, and online status. Use this tool to identify which device to target for further operations.

    **Tool name:** `@Look up device with Fleet`

    **Common use cases:**

    * Find user's device before running diagnostics
    * Verify device ownership
    * Get device identifiers for troubleshooting
    * Check if device is online

    **Example rule:**

    <Prompt description="Fleet device lookup rule">
      When a user reports device issues, use @Look up device with Fleet
      to get their device information. If the device is offline, inform
      the user and create a ticket for IT support. If online, proceed
      with diagnostics.
    </Prompt>
  </Accordion>

  <Accordion title="Check device health">
    Checks comprehensive device health metrics including battery status, disk encryption, MDM enrollment, OS updates, and uptime. Returns detailed health information for security and compliance validation.

    **Tool name:** `@Check device health with Fleet`

    **Common use cases:**

    * Verify security compliance before access approval
    * Diagnose device health issues
    * Check disk encryption status
    * Validate MDM enrollment

    **Example rule:**

    <Prompt description="Fleet device health check rule">
      When approving access requests, use @Check device health with Fleet
      to verify the device meets security requirements. If disk encryption
      is disabled or OS updates are needed, inform the user they must
      address these issues before approval.
    </Prompt>
  </Accordion>

  <Accordion title="Run query">
    Executes predefined diagnostic queries on user devices to gather specific system information. Supports multiple query types for troubleshooting and analysis.

    **Tool name:** `@Run query with Fleet`

    **Available query types:**

    * System information
    * OS version details
    * Logged in users
    * Running processes
    * Network interfaces
    * Disk space usage
    * Recent items

    **Common use cases:**

    * Advanced device troubleshooting
    * Custom system information gathering
    * Security investigation queries
    * Performance diagnostics

    **Example rule:**

    <Prompt description="Fleet performance diagnostics rule">
      When a user reports slow device performance, use @Look up device
      with Fleet to get their device, then @Run query with Fleet to check
      running processes and disk space. Analyze the results and provide
      troubleshooting steps based on what you find.
    </Prompt>
  </Accordion>

  <Accordion title="List saved queries">
    Retrieves the list of available saved queries configured in Fleet. Use this to discover which diagnostic queries are available for troubleshooting.

    **Tool name:** `@List saved queries with Fleet`

    **Common use cases:**

    * Discover available diagnostic queries
    * Reference query names in troubleshooting
    * Guide users on diagnostic capabilities
  </Accordion>
</AccordionGroup>

***

## Setup

<Steps>
  <Step title="Install Fleet integration">
    Follow the [Fleet setup guide](/integrations/fleet/setup) to connect your Fleet instance to Ravenna.
  </Step>

  <Step title="Configure agent">
    Navigate to your agent's settings and ensure Fleet tools appear in the Tools section under Capabilities.
  </Step>

  <Step title="Create rules">
    Write <Tooltip headline="Agent rules" tip="Natural language instructions defining agent behavior" cta="Learn about agent rules" href="/documentation/automate/agents/configure#rules">rules</Tooltip> that reference Fleet tools using @ mentions.
  </Step>

  <Step title="Test tools">
    Test your rules in a controlled environment to verify tools work as expected.
  </Step>
</Steps>

***

## Best practices

* Always use `@Look up device with Fleet` before running queries to ensure you have the correct device
* Combine multiple tools in a single rule for comprehensive diagnostics
* Provide clear instructions to users based on tool results
* Check device online status before running queries
* Consider security compliance checks for access request workflows

<Callout icon="link" color="#6B7280">
  Learn more about [configuring agents](/documentation/automate/agents/configure) and writing effective rules
</Callout>