> ## Documentation Index
> Fetch the complete documentation index at: https://docs.getthread.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Super Magic Tool Reference
> Canonical reference of every Super Magic tool — tickets, scheduling, knowledge, devices, integrations — with read/write type and admin gating per action.
Availability: This is the canonical reference for every tool Super Magic can use — in Inbox chat and over the Thread MCP server (the two surfaces expose the same tools under the same names, filtered by the same permissions).
### How to read this reference
| Column | Meaning |
| ------ | ------------------------------------------------------------------ |
| Tool | The tool id (identical in-product and over MCP) |
| Type | Read (never prompts) or Write (always shows a Confirm action card) |
| Gating | What controls whether a member sees this tool |
**Gating values:** **Always on** (every member, cannot be disabled) · **Write toggle** (on/off per tool; member must also pass the write-access level) · **Admin-only** · **Integration** (configured + toggle on; some are *Limited release*) · **Platform** (managed by Thread).
### Tickets
| Tool | Type | Gating | Notes |
| ------------------------ | ----- | ------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| search\_tickets | Read | Always on | Filters: keywords, client, board, state, dates, priority, contact, member, sentiment; single-ticket lookup by internal or PSA id; optional full message thread (see note below on note visibility); count-only mode |
| list\_boards | Read | Always on | Resolves board names → ids |
| list\_ticket\_statuses | Read | Always on | Statuses valid for a board |
| list\_ticket\_priorities | Read | Always on | |
| list\_ticket\_categories | Read | Autotask workspaces only — hidden elsewhere | The workspace's active ticket categories; resolves names → ids for set\_ticket\_category |
| list\_recap\_templates | Read | Always on | Recap templates available to the workspace |
| create\_ticket | Write | Write toggle | Requires title, board, client; optional contact/assignee |
| update\_ticket | Write | Write toggle | Title, status, priority, board, member assignee (assign/unassign) |
| assign\_contact | Write | Write toggle | Assign, change, or unassign the ticket's **contact** (requester) — resolve with search\_contacts first |
| set\_ticket\_category | Write | Write toggle · Autotask workspaces only | Sets the ticket's PSA category; pair with list\_ticket\_categories |
| add\_ticket\_note | Write | Write toggle | Internal (staff-only) or external (client-visible, synced to PSA) |
| merge\_ticket | Write | Write toggle | ConnectWise workspaces only — hidden elsewhere |
| send\_approval | Write | Write toggle | Emails a contact to approve/decline — route to specific contacts or by contact type |
| log\_time\_entry | Write | Write toggle | Records time in the PSA, optionally marked as the resolution |
| run\_assistive\_ai | Write | Write toggle | Auto title / priority / categorization / recap in a single call |
### Scheduling
| Tool | Type | Gating | Notes |
| ----------------------- | ----- | ------------ | ------------------------------------------------------------------------------------------------------------ |
| list\_schedule\_entries | Read | Always on | Lists a ticket's existing schedule entries |
| schedule\_ticket | Write | Write toggle | Books a technician to a date/time — lands on the Planner + PSA dispatch calendar (does not write to Outlook) |
| update\_schedule\_entry | Write | Write toggle | Modify, reassign, mark done, or delete an entry |
Bounds for mass operations: chained requests run up to \~30 agent steps per message, and `search_tickets` returns up to 100 tickets per call (20 by default; up to 10 when full message threads are included). Batch bigger jobs in chunks.
What `search_tickets` reads from a ticket's thread: when `search_ticket_notes` is `true`, keyword matching and returned message text cover the last 10 client and technician messages on the ticket. It does **not** read internal notes (staff-only notes, including the internal notes written by `log_time_entry`) and it does **not** read PSA time-entry records. Super Magic has no read tool for time entries — `log_time_entry` writes them but nothing surfaces the existing entries back. If you need time-entry data (including internal time notes), pull it from your PSA directly.
### Search & lookups
| Tool | Type | Gating | Notes |
| ----------------------- | ---- | ----------------------------- | --------------------------------------------------- |
| search\_clients | Read | Always on | Resolves client companies → ids |
| search\_contacts | Read | Always on | People at a client; includes learned contact memory |
| search\_members | Read | Always on | Workspace staff |
| search\_thread\_docs | Read | Always on | Thread product documentation |
| search\_knowledge\_base | Read | (Limited release) | Workspace KB + resolved-ticket history |
| search\_itglue | Read | Integration (Limited release) | IT Glue documentation |
| search\_hudu | Read | Integration (Limited release) | Hudu KB, passwords, network docs |
| web\_search | Read | Platform | Live web results (error codes, CVEs, vendor docs) |
**IT Glue write (where enabled):** `push_knowledge_to_itglue` (Write) exports a resolved-ticket knowledge article into IT Glue. It only appears where IT Glue is connected, its Super Magic access is on, and IT Glue export is enabled for the workspace — so most workspaces see IT Glue as read-only search only.
### Intents — admin-only
| Tool | Type | Gating |
| ------------------------- | ----- | ------------------------------------------- |
| list\_intents | Read | Admin-only |
| get\_intent | Read | Admin-only |
| create\_intent | Write | Admin-only + write toggle ( intent\_tools ) |
| update\_intent | Write | Admin-only + write toggle ( intent\_tools ) |
| update\_variation | Write | Admin-only + write toggle ( intent\_tools ) |
| set\_variation\_replies | Write | Admin-only + write toggle ( intent\_tools ) |
| set\_variation\_arguments | Write | Admin-only + write toggle ( intent\_tools ) |
### Flows — admin-only
| Tool | Type | Gating |
| ------------------------------------- | ----- | ----------------------------------------- |
| list\_flows | Read | Admin-only |
| get\_flow | Read | Admin-only |
| create\_flow | Write | Admin-only + write toggle ( flow\_tools ) |
| update\_flow | Write | Admin-only + write toggle ( flow\_tools ) |
| list\_flow\_actions | Read | Admin-only |
| list\_flow\_filter\_attributes | Read | Admin-only |
| list\_flow\_filter\_attribute\_values | Read | Admin-only |
### NinjaOne — integration *(Limited release)*
Requires: NinjaOne configured by an admin **and** the member signed in with their own NinjaOne account. Tools act with **that member's NinjaOne permissions**.
| Tool | Type | Notes |
| ----------------------------------- | ----- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| list\_ninjaone\_organizations | Read | Client orgs in NinjaOne |
| search\_ninjaone\_devices | Read | Filter by `organization_id`, a text `query` (matches device name or last-logged-in user), and/or `device_class` — any one is enough. `device_class` accepts exact NinjaOne classes (`LINUX_SERVER`, `WINDOWS_WORKSTATION`, `NMS_FIREWALL`, …) or group words that expand to several (`SERVER`, `WORKSTATION`, `LINUX`, `WINDOWS`, `MACOS`, `NETWORK_DEVICE`, …); plurals like "Linux servers" work. When combined with `query`, filtering is by class first, then the text is matched in memory over that set. A `device_class` search never falls back to a global name search. |
| get\_ninjaone\_device | Read | Device detail |
| get\_ninjaone\_device\_link | Read | Deep link to the device in NinjaOne |
| get\_ninjaone\_device\_activities | Read | Recent device activity |
| list\_ninjaone\_alerts | Read | |
| list\_ninjaone\_windows\_services | Read | |
| reboot\_ninjaone\_device | Write | |
| set\_ninjaone\_device\_maintenance | Write | Maintenance mode on/off |
| reset\_ninjaone\_alert | Write | |
| control\_ninjaone\_windows\_service | Write | Start/stop/restart a Windows service |
| set\_ninjaone\_device\_approval | Write | Approve/reject a device |
### TimeZest — integration
| Tool | Type | Notes |
| ------------------------------------- | ----- | -------------------------------------------- |
| list\_timezest\_resources | Read | |
| list\_timezest\_appointment\_types | Read | |
| create\_timezest\_scheduling\_request | Write | Sends a real scheduling email to the contact |
| get\_timezest\_scheduling\_requests | Read | |
### Liongard — integration *(Limited release)*
Liongard tools are fetched dynamically from your Liongard instance, so the exact list depends on what Liongard exposes (environments, systems, metrics, alerts, detections, timelines, reports). All Liongard tools are reads. Liongard is also offered as a per-member connector.
### ImmyBot — integration *(Limited release)*
Requires: ImmyBot configured by an admin **and** its Super Magic access toggled on. ImmyBot is workspace-level — there is **no per-member sign-in**; every member sees the same ImmyBot context.
| Tool | Type | Notes |
| ------------------------------------ | ----- | -------------------------------------------------------------------- |
| list\_immybot\_tenants | Read | Client tenants in ImmyBot |
| search\_immybot\_computers | Read | |
| get\_immybot\_computer | Read | Computer detail |
| list\_immybot\_maintenance\_sessions | Read | Recent maintenance sessions |
| run\_immybot\_maintenance\_session | Write | Runs an ImmyBot maintenance session — behind the Confirm action card |
### Dispatch *(where enabled)*
| Tool | Type | Gating | Notes |
| ----------------- | ----- | ------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| get\_next\_thread | Write | Write toggle · available where Auto-Dispatch is enabled | Pulls the next highest-priority ticket from your Auto-Dispatch queue and assigns it to you, like the "Get thread" button in Inbox. Interactive chat only — never runs in an unattended Flow |
See **Super Magic** and **Integrations** updates in the [changelog](/changelog/q3-2026).
## Related topics
- [Thread MCP, the tool reference, and the API](/start-here/roles/automation-engineer/thread-mcp-and-api.md)
- [Thread MCP Server: Developer Guide](/super-magic/thread-mcp-server-developer-guide.md)
- [Use ConnectWise RMM with Super Magic](/super-magic/connect-connectwise-rmm.md)