Trackunit IrisX

Delete all metadata recommendations for an asset in the current account. Returns whether recommendations were deleted, not found, or the caller is not permitted to modify the asset.

sustainability_delete_recommendations

Delete a custom field value for the current account. Important for LLMs: - If the user intent is to clear a value (they provide an empty or null value), call custom-fields_delete_value(valueId). - To obtain valueId, first fetch the existing value for the given entity + definition. - FILE values are also cleared with this tool. Do not pass a file UUID to custom-fields_create_or_update_value to remove a file.

custom-fields_delete_value

Permanently delete a group. This is destructive and cannot be undone through this interface. Members are not deleted — only the group and its memberships. System-managed groups cannot be deleted. **Returns:** A confirmation with the deleted group's ID.

organization_delete_group

Permanently delete a user. This is destructive and cannot be undone through this interface. The account owner cannot be deleted. **Returns:** A confirmation with the deleted user's ID.

organization_delete_user

Dismiss open asset events for a specific asset within a time range in the current account. If eventIds is provided, only those matching events are dismissed; otherwise, all open events within the time range are dismissed. The time range can span at most 400 days and must contain at most 1000 open events — narrow the range if either limit is exceeded. Returns the IDs of the dismissed events.

eventlog_dismiss_asset_events

Execute a read-only GraphQL query. REQUIRED: introspect the schema first, then submit exactly one named query operation (for example, `query GetAsset { ... }`). Anonymous operations, mutations, and subscriptions are rejected. When results include supported Trackunit entities, use explore_get_manager_urls and present them as Manager links. Returns data or validation errors. Requires authentication.

explore_execute_gql_query

Generate one Manager Goto URL for a filtered Asset list or Map view from a raw GraphQL `AssetFiltersInput`. Choose `map` when location, position, geospatial area, or similar spatial context is central to the answer. Choose `assets` for non-spatial asset subsets. Before calling this tool, introspect the GraphQL schema and/or validate a query that uses the same `AssetFiltersInput` so the field names and shapes are valid. Returns exactly one URL.

explore_get_asset_filtered_manager_url

Get a presigned upload URL and HTTP contract for a FILE custom field on the current account. End-to-end FILE flow for agents: 1. Create or locate a FILE definition (custom-fields_create_definition with type FILE, or GraphQL query customFieldDefinitions). 2. Call this tool with that definitionId and the entityId the file should be attached to. 3. HTTP POST multipart/form-data to the returned uploadLink. Put the file in form field "file". The filename must use an allowed extension from the tool output (for example .pdf, .jpg, .png, .json). Maximum file size is 20 MB. Do not PUT raw bytes, do not wrap the file in JSON, do not send a file UUID, and do not send an Authorization header (the token is in the URL). 4. After HTTP 200, the FILE value is created or replaced automatically. Do not call custom-fields_create_or_update_value to confirm. 5. Responses on FILE values may include uploadLink (POST multipart here to replace the file) and downloadLink (GET the current file). The value field is the stored file reference UUID and must not be sent as input. 6. To clear a FILE value, use custom-fields_delete_value(valueId). The definition must be of type FILE. This tool only returns the upload URL and HTTP contract; it does not upload file bytes.

custom-fields_get_file_upload_link

Generate Trackunit Manager URLs for one or more host entities. When your research finds supported Trackunit entities, collect them and call this tool once near the end before responding. In the final response, always present supported entities as clickable Manager links using each returned `url`.

explore_get_manager_urls

Issue a short-lived Mapbox access token for the Trackunit map app to render styles and tiles.

explore_get_mapbox_token

Search the GraphQL schema for types, fields, and input objects matching given keywords. Returns complete type definitions in SDL format including input types, argument types, and connection patterns. Always include both singular and plural keyword variants. Call this before writing/executing any GraphQL query.

explore_introspect_gql_schema

List all Databricks Genie spaces available to the current IrisX Analytics user. Use this discovery tool before querying Genie so you can choose an accessible spaceId.

ixa_genie_list_spaces

Poll for a Databricks Genie response using the spaceId, conversationId, and messageId returned by ixa_genie_query_space.

ixa_genie_poll_response

Ask a natural-language question against a Databricks Genie space. Call ixa_genie_list_spaces first to choose an accessible spaceId. The response includes conversationId/messageId references that can be passed to ixa_genie_poll_response.

ixa_genie_query_space

Execute read-only SQL queries in Databricks Unity Catalog. This tool executes SQL in Databricks SQL (DBSQL), so use DBSQL syntax. Unity Catalog uses a three-level namespace: catalog.schema.table. Always use fully qualified names (e.g., catalog.schema.table) in your queries for reliable access. Use backticks to escape names with special characters: catalog.schema.`special-table`. For long-running queries, this tool will return a statement_id that can be used to poll for results. Catalogs: Machine and telematics data provided by Trackunit for the customer (assets, fleet, sites, utilization, etc.) lives in the `irisx` catalog — always start there. Other catalogs named similarly to the customer are for tables the customer uploads themselves, not the data Trackunit provides. Do not guess catalog names from the account slug — prefer `irisx` unless the user explicitly asks about their own uploaded tables. To discover available data assets, use the following commands: 1. 'SHOW SCHEMAS IN irisx' (or 'SHOW CATALOGS' only when you need customer-uploaded catalogs) 2. 'SHOW TABLES IN irisx.schema_name' to list tables in a schema 3. 'DESCRIBE TABLE irisx.schema_name.table_name' to view table structure and columns

ixa_sql_execute_read_only

Poll for the results of a long-running SQL query using its statement ID. Use this tool when ixa_sql_execute_read_only returns a statement_id for a query that didn't complete immediately.

ixa_sql_poll_result

Report an issue on an asset, mirroring the "Report issue" action in Trackunit Manager. Use it to record a problem observed on a machine, such as damage or a malfunction, so that it shows up in the asset's event log. Supported asset types are MACHINE, VEHICLE, and GATEWAY; EQUIPMENT, ATTACHMENT, TOOL, and OTHER assets do not support issue reporting. A critical issue also puts the asset on the Attention List, while a non-critical one only appears in the asset's event history. Returns the identifier of the created issue. Fails if the asset does not support issue reporting or the title or description is empty.

asset-issues_report_issue

Report feedback about the Trackunit IrisX MCP itself — its tools, their results, or the capabilities it is missing. This channel is scoped to this server only; do not use it to comment on other services, data sources, or the application you are running inside. Reach for it in two situations: proactively, when you hit a real problem here (a tool that errors out, a result that is clearly wrong or unhelpful, or functionality that simply does not exist yet); and on demand, whenever a user asks you to pass along feedback. One hard rule: the content must contain no personal data. Remove anything that could point to a real person — names, emails, phone numbers, addresses, birth dates, identifiers, payment details, and the like — and swap in neutral placeholders like '[name]' or '[email]' before submitting.

send_feedback

Apply the access-management mode (the lock/start state) to one or more assets in a single call. Possible modes: UNLOCKED_FOR_ALL (asset can be started), UNLOCKED_FOR_KEY (asset can be started only after unlocking it with a PIN/mobile phone), LOCKED_FOR_ALL (asset cannot be started). At most 100 assets per call. Assets are scoped to the caller's account. The change is dispatched asynchronously; no tracking id is returned for mode changes. Returns a per-asset summary of accepted assets (tracking id is null for mode changes) and rejected assets (with a reason).

digital-key_set_access_management_mode

Apply immobilizer configuration (immobilizer mode and/or key valid/expire times) to one or more assets in a single call. Only provided (non-null) fields are set; any omitted field falls back to the asset's most recently requested immobilizer configuration, or to service defaults if it has never been configured. At most 100 assets per call. Assets are scoped to the caller's account. Returns a per-asset summary of accepted assets (with a tracking id for the dispatched change) and rejected assets (with a reason).

digital-key_set_immobilizer_configuration

Show a compact, clickable list of Trackunit Manager entities (asset, site, customer, group) so the user can browse, compare, or open them in Manager. Each row shows the entity name, key details, optional thumbnail, and an optional labeled datapoint column. Pass up to 100 known entities by type and ID. Use when presenting a list of compatible entities with at most one shared datapoint; find entity IDs with GraphQL first if needed. Renders inline — user sees all rows. Don't repeat rows in your reply unless the user asks; use returned row data for follow-ups.

explore_show_entity_list

Render a map of assets and sites using latest known asset locations and active site geometries. Use boundingBox or coordinate alone to show all assets in an area. Use assetIds, assetTypes, assetSubtypes, or filters to show only matching assets. Use siteIds, siteNameContains, or siteTypes to show matching sites and the assets assigned to them.

explore_show_map

Update the caller's own account: name, postal address and contact details. The account is always the one in the caller's token; another account is targeted by impersonating it, never by naming it. Omitted fields are left unchanged, and blank values are rejected — this tool cannot clear a field. Changing the contact email also updates the account owner user's email. **Returns:** The updated account with its id, name, address and contact details.

organization_update_account

Update an asset for the current account (partial update — only the fields provided are changed). The asset is identified by the chosen identifier type and value. To update by UUID, set `identifierType` to **ASSET_ID** and `identifierValue` to the asset UUID. To explicitly clear (set to null) an optional field, include its name in `fieldsToClear` — passing a null parameter is treated as "no change", not "clear". **Returns:** Updated asset representation with all current field values.

asset_update

Update an existing ACCOUNT-scoped custom field definition owned by the current account. Important for LLMs: - Use the definitionId of the existing definition to update. - Provide the type discriminator and only mutable properties in the definition patch object. - The type discriminator must match the existing definition; field type and entity type cannot be changed. - Omit translations to leave existing titles unchanged. An empty translations array is rejected because it would wipe the definition's titles; send at least one translation (language + title) to replace them. - Omit scopeType for normal account-specific updates; omitted scopeType preserves the current ACCOUNT scope. - Explicit scopeType ACCOUNT is accepted. - GLOBAL and ACCOUNT_WRITE_GLOBAL_READ definitions cannot be updated through MCP. Use the Custom Fields API for those scopes.

custom-fields_update_definition

Update a group: rename it, change its description, and add or remove asset and user members. Membership changes are deltas — ids already in the requested state are no-ops, so repeating a call is safe. Omitted fields are left unchanged. The caller must have view permission on every asset added. **Returns:** A confirmation with the updated group's ID.

organization_update_group

Rename a user (change their display name). The user's role, email and permissions are never changed by this tool. Use update_user_role to change a user's role. **Returns:** The updated user with its current name, email, role and status.

organization_update_user

Set or change a user's role to one of the existing roles. This changes what the user is allowed to do and takes effect immediately; it cannot be undone through this interface (though a new role can be assigned again). No other user attribute is touched. Use update_user to rename a user. **Returns:** The updated user with its current name, email, role and status.

organization_update_user_role