Cited IBM Maximo and MAS answers: upgrades, error codes, gotchas, versions and lifecycle.
Scored across 19 tools
Most tools target distinct query surfaces, but there is noticeable overlap among the change/history tools (change_watch, maximo_changelog, behaviour_history) and between lifecycle_dates and support_lifecycle. The descriptions help separate them, but an agent could still mis-select in those clusters.
All names are snake_case and domain-readable, but the set mixes imperative verbs (ask, get, list, lookup, search) with noun-phrase names (behaviour_history, deprecation_register, maximo_changelog, upgrade_plan). There is no single verb_noun convention, though the names still communicate intent.
At 19 tools this is a heavy surface for an agent to scan, and some tools could be consolidated, such as support_lifecycle/lifecycle_dates and change_watch/maximo_changelog. The broad Maximo upgrade and knowledge domain makes the count defensible, but it is on the borderline.
Coverage is strong for a read-only knowledge server: search, record retrieval, version scoping, upgrade planning, comparisons, change/deprecation history, lifecycle dates, mobile topics, gotchas, and corpus stats are all represented. Minor gaps exist, such as no general browse-all endpoint or per-source document listing, but agents have no dead ends for core tasks.
Answer a practical IBM Maximo question from Assetize’s published, source-backed knowledge. The answer cites its evidence ([R#] markers with source URLs) and DECLINES when the published record cannot support one — it never guesses. Best for how-to, troubleshooting, version-behaviour and error questions.
Inputs: question (required), version.
Historical, lifecycle, behaviour-change, deprecation, architecture and API records — the "how did this get here / when does it end" archaeology. Same data as assetize.com.au/archaeology.
Inputs: limit, version.
The curated feed of genuinely material IBM Maximo / MAS 9.x changes — security, upgrades, deprecations, releases, behaviour and migration breaks. Each carries What Changed / Why It Matters, previous behaviour, a version comparison, a clearly-labelled Assetize interpretation (never presented as IBM’s), the IBM sources, and the corpus records that grounded it. Pass a slug for one change in full; omit it to list, optionally filtered by category. Same data as assetize.com.au/change-watch.
Inputs: slug, limit, category.
Compare two Maximo versions/eras and get a cited upgrade-impact report per functional area: changes to absorb (deprecations, behaviour changes, API changes, gotchas), fixes/APARs since, and newly announced capability — the last two reported as context only, never scored as upgrade work. Same reviewed, source-backed comparison and ranking as assetize.com.au/compare. Accepts either a version label ("7.6.1.3", "9.2") or bucket id ("9-2"). Known buckets: 7.6.1.3, 7.6.x (classic Maximo 7.6/7.6.1/7.6.1.x), 8.x (Maximo Application Suite 8), 9.0, 9.1, 9.2.
Inputs: to (required), from (required).
Coverage / transparency stats for the Assetize corpus: published records, unique source documents, versions represented, and raw evidence items.
Inputs: no named parameters.
What was deprecated, removed or renamed in Maximo / MAS, in which version, what IBM says replaces it (blank when IBM has not named one), and the published records that say so. Curated; rows publish only on evidence. Same data as assetize.com.au/upgrade/deprecations.
Inputs: kind.
Every FIX and SECURITY record the 9.x change log holds for the releases inside a move (the 9.x log starts at 9.1). Optionally one functional area. Counted, never scored as upgrade weight.
Inputs: to (required), from (required), area, limit.
Fetch one published record by slug: the established fact, claims, version scope, and every cited source URL.
Inputs: slug (required).
End-of-support, Extended Support and Dual Support dates for Maximo and MAS as structured rows: product, version, milestone, ISO date, days remaining, and the IBM page each comes from. Optionally scope by product or version. Same data as assetize.com.au/upgrade/deadlines.
Inputs: product, version.
Known traps, upgrade landmines, installation issues, security and troubleshooting records — optionally scoped to a version. Same data as assetize.com.au/gotchas.
Inputs: limit, version.
Find published records about a specific Maximo error or fix identifier (BMXAA1234E, IJ12345, APAR...).
Inputs: code (required).
The dated, source-cited log of what changed across IBM Maximo / MAS 9.x (9.1 onward): deprecations, behaviour changes, API/fixes, security, gotchas, upgrades, lifecycle and releases. Only real change records (never data-dictionary noise) and nothing the curator demoted. Same data as assetize.com.au/changelog. Optionally filter by version ("9.1", "9.2") and/or type.
Inputs: type, limit, version.
Researched IBM statements about Maximo Mobile, by topic: what it is, the shell and Graphite-app architecture, device requirements (OS levels, memory, WebView2, ARCore, shared devices), getting the app onto devices (stores, MSIX, QR server URL, MDM), login and shared devices, data sync and attachments, administration (Mobile Configuration app, properties), the apps release by release (8.11, 9.0, 9.1, 9.2), push notifications, and coming from Maximo Anywhere or 7.6.1. Every fact carries IBM's verbatim sentence, page and read date. Scope by release and/or topic. Same data as assetize.com.au/mobile. For fixes and gotchas use search_records.
Inputs: topic, version.
Every published record scoped to a given Maximo version or family (e.g. "9.2", "7.6.1"). Same data as assetize.com.au/maximo/.
Inputs: version (required), limit.
Fast keyword search over published Assetize knowledge records. Returns slugs, titles and short answers with record URLs.
Inputs: query (required), limit, version.
IBM Maximo / MAS support-lifecycle facts: end-of-support / Extended Support transitions and the 2026/2027 deadlines, drawn from source-backed lifecycle records and the curated Change Watch. Optionally scope to a version.
Inputs: limit, version.
Statically check a WORKORDER Object launch point Automation Script (Jython or JavaScript) against one release lens's real MXAPIWODETAIL dictionary. Extracts every attribute the script references via mbo.getString/setValue/isNull/getInt/getDate/getBoolean, then reports which ones the named lens has evidence for. Static evidence only — it does not run the script. A missing attribute is reported NOT_ASSESSED, never claimed as a runtime failure; for a real pass/fail/skip verdict, run the CLI (mvn verify) or the browser runner at assetize.com.au/test-stubs/automation-scripts. Lenses: 761 (Maximo 7.6.1), mas811 (MAS 8.11), mas90 (MAS 9.0), mas91 (MAS 9.1), mas92 (MAS 9.2).
Inputs: lens (required), source (required).
The phased checklist (before / during / after) for one Maximo move. Every item is CITED — its published records are resolved against the corpus on this call and an item whose records are not published is dropped — or VERIFY, a level-dependent question to settle against IBM. Optionally one phase.
Inputs: to (required), from (required), phase.
One Maximo move from an earlier catalogue release to a later one (7.6.1, 8.11, 9.0, 9.1, 9.2), composed from the published record: the support clock on the source release, the staged route (IBM's n-1 policy), what IBM says about the move (route, platform, database, Java, users, add-ons, reports; each with IBM's words and page), the few items only the customer's own system can answer, break-class changes (deprecations, behaviour changes) and landmines (upgrade notes, gotchas) in range from the 9.x change log, fix and security counts, the deprecation-register rows touching the range, and the curated Change Watch entries. Every item links its record or IBM page. Same composition as assetize.com.au/upgrade//.
Inputs: to (required), from (required).
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Read-only, source-linked AI, architecture, governance and technical product articles from AI TPM.
One governed MCP endpoint for 40+ business systems. Read-only, source-cited answers.
RunbookDesk: the site's own MCP server — dataset; every answer cites the site.
Upkeepvo: the site's own MCP server — dataset; every answer cites the site.
Add one secure layer between your agents and this server.
