Super Magic Tool Reference

Availability: This is the canonical reference for every tool Super Magic can use, in Inbox chat and over the Thread MCP server. A tool exposed on both surfaces keeps the same name and the same permissions, but Thread MCP exposes a curated subset: Liongard tools and per-member connector tools (Linear, Notion, Zapier) are available in Super Magic only.

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; `has_parent` narrows to child tickets (merged or bundled into a parent) or standalone tickets only; single-ticket lookup by internal or PSA id (multi-id lookups cap at 50 ids); optional full message thread (see note below on note visibility); count-only mode; `group_by` (`client`, `board`, `status`, `priority`, or `assignee`) returns per-group counts plus a total instead of rows (most common first, up to 50 groups with the rest rolled into an `other` bucket). Search listings page at 50 tickets: a partial page carries `has_more: true` plus `total` and `next_cursor`; pass `next_cursor` back as the `cursor` parameter (with the same filters and sort) to continue, or narrow the filters. See the bounds note below
list_boards	Read	Always on	Resolves board names → ids
list_ticket_statuses	Read	Always on	Statuses valid for a board. Call with `internal_ticket_id` to list the ticket’s board statuses plus the ticket’s current status, or with `board_id` (from list_boards) to list a board’s statuses without a ticket, which is how create and merge flows resolve a status id before the ticket exists. Passing both uses the ticket’s board and notes that the board id was ignored
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_board_classifications	Read	ConnectWise and HaloPSA workspaces — hidden elsewhere	The active classification values for a ticket’s board, read from synced data. ConnectWise: the Type → Subtype → Item tree. HaloPSA: a flat list of Category 1 values (see note below on HaloPSA semantics). Optional name filter; reports the ticket’s current classification; resolves names → ids for set_ticket_classification
list_recap_templates	Read	Always on	Recap templates available to the workspace
create_ticket	Write	Write toggle	Requires title, board, client; optional contact/assignee (the assignee must be an active member)
update_ticket	Write	Write toggle	Title, status, priority, board, member assignee (assign/unassign). Deactivated members can be unassigned but not assigned
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
set_ticket_classification	Write	Write toggle · ConnectWise and HaloPSA workspaces	ConnectWise: sets the ticket’s Type, Subtype, and Item (see note below on the id cascade). HaloPSA: sets the ticket’s Category 1 (see note below on HaloPSA semantics). Pair with list_board_classifications
add_ticket_note	Write	Write toggle	Internal (staff-only) or external (client-visible, synced to PSA); can @-mention members via `mention_member_ids` (ids from search_members) — mentioned members are notified and added to the thread; can @-mention contacts via `mention_contact_ids` (ids from search_contacts) on external notes only — mentioned contacts must belong to the ticket’s client company and are added to the thread and the PSA ticket, but receive no notification
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. `note_type` (`internal` or `external`) overrides the workspace Timepad default for this entry; omitted, the workspace default applies. `work_type` takes the PSA work type by name (resolved against the workspace’s active work types) and falls back to the ticket → agreement → company default when omitted; unknown names are rejected with the valid names listed. Work type applies on ConnectWise and Autotask; HaloPSA does not accept a work type, so `work_type` is a no-op there
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 Planner schedule entries for a date range, optionally filtered by member or ticket. Entries whose only assignees are deactivated members are excluded, and a deactivated co-assignee on a shared entry is never named
schedule_ticket	Write	Write toggle	Books a technician to a date/time — lands on the Planner + PSA dispatch calendar (does not write to Outlook). Can’t book a deactivated member
update_schedule_entry	Write	Write toggle	Modify, reassign, mark done, or delete an entry. Reassignment requires an active member; unassigning a deactivated member still works

How set_ticket_classification resolves ids: ConnectWise stores Type, Subtype, and Item as one chain, so the tool takes the deepest id you pass and derives the levels above it. Passing item_id alone sets all three without disturbing the existing Type or Subtype; passing subtype_id alone sets Type + Subtype and clears the Item; passing type_id alone sets the Type and clears the Subtype and Item. Mismatched combinations (an id under a different parent) are rejected. Always resolve ids with list_board_classifications first.

HaloPSA semantics for the classification tools: HaloPSA has a single Category 1 value instead of a Type / Subtype / Item chain. list_board_classifications returns the Category 1 values for the ticket’s board as a flat list, and set_ticket_classification takes type_id alone, passing subtype_id or item_id is rejected. When a HaloPSA ticket type restricts which Category 1 values it accepts, the list contains only the allowed values, and setting a value outside them is rejected with the ticket type named. These tools never change the HaloPSA ticket type itself; that is a separate field.

Bounds for mass operations: chained requests run up to ~30 agent steps per message, and search_tickets returns at most 50 tickets per page (20 by default; up to 10 when full message threads are included). Multi-id lookups also cap at 50 ids. A partial page always sets has_more: true and includes total and next_cursor; a full-page response is not the full set until has_more is false. To continue the same search, resend the same filters and sort and pass next_cursor back as the cursor parameter. cursor is for search listings only. It cannot be combined with an id lookup, group_by, or count_only, and a cursor whose filters or sort don’t match the original search is refused. Prefer narrowing filters, group_by, or count_only over deep paging.

How much of a ticket’s thread comes back with include_messages: when include_messages is true, each ticket in the response carries its message thread (external and internal notes, ordered by date, most recent kept). A single-ticket result carries up to the 75 most recent notes; a multi-ticket result carries up to 20 per ticket. A trimmed thread also carries total_messages and messages_truncated — check them before assuming you have the whole thread, and re-fetch the ticket on its own by id to reach the earlier notes. Ticket page size also drops to 10 when include_messages is on (see the bounds note above).

What search_tickets reads from a ticket’s thread for keyword matching: when search_ticket_notes is true (a separate flag from include_messages), 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; each result includes a `types` list with the client’s PSA company type(s) (for example Prospect, Managed Services — names come from your PSA, not a fixed set). HaloPSA clients have at most one type, taken from the client’s Customer Type field in HaloPSA (often industry values such as Education or Retail). An empty list means no type is assigned in the PSA
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; results include `source_updated_at`, the date the document was last updated in IT Glue itself (omitted when IT Glue has no timestamp for a document)
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.

Triage Agent

Triage Agent tools are gated on the workspace’s Triage Agent setting: they only appear when the Triage Agent is enabled for the workspace. They are exposed in Super Magic in Inbox and over the Thread MCP server.

Tool	Type	Gating	Notes
get_triage_agent_settings	Read	Triage Agent enabled	Returns the workspace’s Triage Agent configuration (personality, message size, Issue Identification Framework selections)
get_triage_agent_session	Read	Triage Agent enabled	Loads the Triage Agent session for one ticket: how the session ended and the full conversation transcript including the agent’s tool calls. Use it to explain why the Triage Agent said or did something on a ticket. Requires `internal_ticket_id` (from search_tickets results)
save_triage_custom_rule	Write	Triage Agent enabled + write toggle	Create, update, or delete a Triage Agent Custom Rule; supports targeting by client, company type, contact type, parent company, or top-level company
update_triage_agent_settings	Write	Triage Agent enabled + write toggle	Updates the workspace’s Triage Agent personality, message size, or Issue Identification Framework selections

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.

Super Magic only. Liongard tools are not exposed over the Thread MCP server, in either form. An external MCP client (Claude, ChatGPT, Cursor) will not list them even when the integration is connected and its Super Magic toggle is on — run Liongard requests in Super Magic in Inbox instead.

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

Magic AI

Magic Agents

Voice AI

Messenger

Thread Inbox

Flows

Agent Builder

Auto Dispatch

Super Magic & Thread MCP

Integrations

Companion Apps

Service Intelligence

Magic Analytics

Workspace administration

Notifications

Security & compliance

Plans & billing

Super Magic Tool Reference

How to read this reference

Tickets

Scheduling

Search & lookups

Triage Agent

Intents — admin-only

Flows — admin-only

NinjaOne — integration (Limited release)

TimeZest — integration

Liongard — integration (Limited release)

ImmyBot — integration (Limited release)

Dispatch (where enabled)

​How to read this reference

​Tickets

​Scheduling

​Search & lookups

​Triage Agent

​Intents — admin-only

​Flows — admin-only

​NinjaOne — integration (Limited release)

​TimeZest — integration

​Liongard — integration (Limited release)

​ImmyBot — integration (Limited release)

​Dispatch (where enabled)

How to read this reference

Tickets

Scheduling

Search & lookups

Triage Agent

Intents — admin-only

Flows — admin-only

NinjaOne — integration (Limited release)

TimeZest — integration

Liongard — integration (Limited release)

ImmyBot — integration (Limited release)

Dispatch (where enabled)