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

# MCP tools and permissions

> Reference the read-only tools exposed by each AutoFire MCP permission.

| Tool                      | Required permission        | Output safeguards                         |
| ------------------------- | -------------------------- | ----------------------------------------- |
| `get_dealership_profile`  | `dealership:read`          | Authorized dealership only                |
| `search_inventory`        | `inventory:read`           | Up to 50 vehicles; no VIN                 |
| `get_vehicle`             | `inventory:read`           | One authorized-dealership vehicle; no VIN |
| `list_leads`              | `leads:read`               | No name, email, phone, message, or notes  |
| `get_lead`                | `leads:read` + `leads:pii` | One lead with contact details             |
| `list_test_drives`        | `test_drives:read`         | No customer contact details or notes      |
| `get_dealership_insights` | `insights:read`            | Aggregate reports only                    |

## Inventory pagination

`search_inventory` accepts an optional text query, vehicle status, `limit` from 1–50, and `offset` from 0–5000. Its default status is `available`.

## Workflow pagination

Lead and test-drive list tools accept an optional status plus a `limit` from 1–50 and `offset` from 0–5000.

## Cross-dealership behavior

Tools derive the dealership from the authenticated key. They never accept a client-provided dealership ID. Requesting a vehicle or lead UUID from another dealership returns no record.

## Read-only contract

The current server does not create, edit, delete, email, text, publish, or submit records. Tool annotations also declare the operations read-only and closed-world.