Server definition

Hash: sha256:446f16005c3a54d616db1b229784aba3aacc398d97aa05b46b3b1214c6178d9f
What it is: What a remote MCP server returned when asked what it offers: 19 tools

The blob, as servednamed by its sha256

{
  "instructions": "Assetize is an evidence-grounded IBM Maximo knowledge base (assetize.com.au). Every answer from ask_maximo is built only from published, source-backed records and carries [R#] citations to the original sources; when the published evidence does not support an answer, the tool says so instead of guessing. Use search_records for fast keyword lookup, lookup_error_code for BMX/IJ error codes, get_record for a full record with sources, compare_maximo_versions for a cited deprecation/behaviour-change/gotcha report between two Maximo versions (same data as assetize.com.au/compare), maximo_changelog for the dated 9.x change log, change_watch for the curated feed of material 9.x changes (each with an explicit, labelled Assetize interpretation and its IBM + corpus evidence), list_gotchas for known traps/upgrade landmines, records_by_version for everything covered at a version, behaviour_history for lifecycle/behaviour-change/deprecation archaeology, support_lifecycle for end-of-support / Extended-Support dates, and corpus_stats for coverage figures. For upgrade planning use the Upgrade Desk tools: upgrade_plan(from, to) composes one move (clock, the staged route, what IBM says about the move with quotes and pages, breaks, landmines, gains, register rows, Change Watch) with record links; upgrade_checklist(from, to, phase?) is the phased checklist whose sourced items are resolved against the published corpus on every call, with the items only your own system can answer marked as such; fixes_gained(from, to, area?) lists the fixes and security changes a move carries; deprecation_register(kind?) lists what was deprecated, removed or renamed and what IBM says replaces it; lifecycle_dates(product?, version?) gives the structured end-of-support / Extended Support dates with days remaining. Catalogue releases: 7.6.1, 8.11, 9.0, 9.1, 9.2. For Maximo Mobile use maximo_mobile(version?, topic?): what IBM says about the mobile product — device requirements, shell and Graphite architecture, offline and sync, login and shared devices, MDM deployment, push notifications, the apps release by release (8.11 to 9.2), and the Anywhere / 7.6.1 exit — each with IBM's words and page; pair it with search_records for fixes and gotchas. Every tool returns only published, source-backed material; IBM statements come with IBM's words, page and read date. test_automation_script_evidence(source, lens) statically checks a WORKORDER Automation Script (Object launch point) against one MXAPIWODETAIL dictionary: which attributes it references, and whether each is evidenced on that lens — CLI-equivalent evidence, not execution (that needs a script host: the CLI or the browser runner at /test-stubs/automation-scripts). Lenses: 761, mas811, mas90, mas91, mas92. For discovery, read the MCP Resources first: assetize://corpus/capabilities describes the server, every tool and every resource; assetize://corpus/versions lists the Maximo versions covered (with record counts) and assetize://corpus/stats the coverage figures; the record/{slug}, version/{version} and error/{code} resource templates read individual published records — so an agent can learn what Assetize covers before calling a tool.",
  "tools": [
    {
      "description": "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.",
      "inputSchema": {
        "additionalProperties": false,
        "properties": {
          "question": {
            "description": "The Maximo question, in plain language.",
            "maxLength": 2000,
            "minLength": 3,
            "type": "string"
          },
          "version": {
            "description": "Optional version scope, e.g. \"9.2\", \"8.11\", \"7.6.1\".",
            "type": "string"
          }
        },
        "required": [
          "question"
        ],
        "type": "object"
      },
      "name": "ask_maximo",
      "outputSchema": null
    },
    {
      "description": "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.",
      "inputSchema": {
        "additionalProperties": false,
        "properties": {
          "limit": {
            "description": "Max results (default 30, max 100).",
            "type": "number"
          },
          "version": {
            "description": "Optional version filter, e.g. \"9.2\".",
            "type": "string"
          }
        },
        "type": "object"
      },
      "name": "behaviour_history",
      "outputSchema": null
    },
    {
      "description": "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.",
      "inputSchema": {
        "additionalProperties": false,
        "properties": {
          "category": {
            "description": "Filter: SECURITY|UPGRADE|DEPRECATION|RELEASE|BEHAVIOUR|MIGRATION|INTEGRATION|SUPPORT.",
            "type": "string"
          },
          "limit": {
            "description": "Max items when listing (default 30, max 60).",
            "type": "number"
          },
          "slug": {
            "description": "A change slug for the full record. Omit to list.",
            "type": "string"
          }
        },
        "type": "object"
      },
      "name": "change_watch",
      "outputSchema": null
    },
    {
      "description": "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.",
      "inputSchema": {
        "additionalProperties": false,
        "properties": {
          "from": {
            "description": "Starting version, e.g. \"7.6.1.3\".",
            "type": "string"
          },
          "to": {
            "description": "Target version, e.g. \"9.2\".",
            "type": "string"
          }
        },
        "required": [
          "from",
          "to"
        ],
        "type": "object"
      },
      "name": "compare_maximo_versions",
      "outputSchema": null
    },
    {
      "description": "Coverage / transparency stats for the Assetize corpus: published records, unique source documents, versions represented, and raw evidence items.",
      "inputSchema": {
        "additionalProperties": false,
        "properties": {},
        "type": "object"
      },
      "name": "corpus_stats",
      "outputSchema": null
    },
    {
      "description": "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.",
      "inputSchema": {
        "additionalProperties": false,
        "properties": {
          "kind": {
            "description": "Optional: DEPRECATION, REMOVAL or RENAME.",
            "type": "string"
          }
        },
        "type": "object"
      },
      "name": "deprecation_register",
      "outputSchema": null
    },
    {
      "description": "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.",
      "inputSchema": {
        "additionalProperties": false,
        "properties": {
          "area": {
            "description": "Optional functional area, e.g. \"WORK_ORDERS\".",
            "type": "string"
          },
          "from": {
            "description": "Source release, e.g. \"9.1\".",
            "type": "string"
          },
          "limit": {
            "description": "Max entries per section (default 40, max 200).",
            "type": "number"
          },
          "to": {
            "description": "Target release, e.g. \"9.2\".",
            "type": "string"
          }
        },
        "required": [
          "from",
          "to"
        ],
        "type": "object"
      },
      "name": "fixes_gained",
      "outputSchema": null
    },
    {
      "description": "Fetch one published record by slug: the established fact, claims, version scope, and every cited source URL.",
      "inputSchema": {
        "additionalProperties": false,
        "properties": {
          "slug": {
            "description": "Record slug from search_records / lookup_error_code results.",
            "type": "string"
          }
        },
        "required": [
          "slug"
        ],
        "type": "object"
      },
      "name": "get_record",
      "outputSchema": null
    },
    {
      "description": "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.",
      "inputSchema": {
        "additionalProperties": false,
        "properties": {
          "product": {
            "description": "Optional product substring, e.g. \"Application Suite\" or \"Asset Management\".",
            "type": "string"
          },
          "version": {
            "description": "Optional version, e.g. \"8.11\", \"7.6.1\", \"9.0\".",
            "type": "string"
          }
        },
        "type": "object"
      },
      "name": "lifecycle_dates",
      "outputSchema": null
    },
    {
      "description": "Known traps, upgrade landmines, installation issues, security and troubleshooting records — optionally scoped to a version. Same data as assetize.com.au/gotchas.",
      "inputSchema": {
        "additionalProperties": false,
        "properties": {
          "limit": {
            "description": "Max results (default 30, max 100).",
            "type": "number"
          },
          "version": {
            "description": "Optional version, e.g. \"9.2\".",
            "type": "string"
          }
        },
        "type": "object"
      },
      "name": "list_gotchas",
      "outputSchema": null
    },
    {
      "description": "Find published records about a specific Maximo error or fix identifier (BMXAA1234E, IJ12345, APAR...).",
      "inputSchema": {
        "additionalProperties": false,
        "properties": {
          "code": {
            "description": "The error/fix code, e.g. \"BMXAA4214E\".",
            "type": "string"
          }
        },
        "required": [
          "code"
        ],
        "type": "object"
      },
      "name": "lookup_error_code",
      "outputSchema": null
    },
    {
      "description": "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.",
      "inputSchema": {
        "additionalProperties": false,
        "properties": {
          "limit": {
            "description": "Max entries (default 200, max 1000).",
            "type": "number"
          },
          "type": {
            "description": "Filter to one change type: DEPRECATION, BEHAVIOUR_CHANGE, FIX, SECURITY, GOTCHA, UPGRADE, LIFECYCLE, RELEASE.",
            "type": "string"
          },
          "version": {
            "description": "Filter to a 9.x line, e.g. \"9.2\". Omit for all of 9.x.",
            "type": "string"
          }
        },
        "type": "object"
      },
      "name": "maximo_changelog",
      "outputSchema": null
    },
    {
      "description": "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.",
      "inputSchema": {
        "additionalProperties": false,
        "properties": {
          "topic": {
            "description": "Optional topic: what, architecture, devices, deploy, auth, sync, admin, apps, notifications, classic.",
            "type": "string"
          },
          "version": {
            "description": "Optional Maximo Mobile release: \"8.11\", \"9.0\", \"9.1\" or \"9.2\". Facts that hold for every release are always included.",
            "type": "string"
          }
        },
        "type": "object"
      },
      "name": "maximo_mobile",
      "outputSchema": null
    },
    {
      "description": "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/<version>.",
      "inputSchema": {
        "additionalProperties": false,
        "properties": {
          "limit": {
            "description": "Max results (default 40, max 200).",
            "type": "number"
          },
          "version": {
            "description": "Version label or family, e.g. \"9.2\".",
            "type": "string"
          }
        },
        "required": [
          "version"
        ],
        "type": "object"
      },
      "name": "records_by_version",
      "outputSchema": null
    },
    {
      "description": "Fast keyword search over published Assetize knowledge records. Returns slugs, titles and short answers with record URLs.",
      "inputSchema": {
        "additionalProperties": false,
        "properties": {
          "limit": {
            "description": "Max results, 1-25 (default 10).",
            "type": "number"
          },
          "query": {
            "description": "Keywords or an exact identifier (MXAPI..., BMX..., module name).",
            "type": "string"
          },
          "version": {
            "description": "Optional version label or family filter, e.g. \"9.2\".",
            "type": "string"
          }
        },
        "required": [
          "query"
        ],
        "type": "object"
      },
      "name": "search_records",
      "outputSchema": null
    },
    {
      "description": "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.",
      "inputSchema": {
        "additionalProperties": false,
        "properties": {
          "limit": {
            "description": "Max results (default 30).",
            "type": "number"
          },
          "version": {
            "description": "Optional version, e.g. \"8.11\", \"9.0\".",
            "type": "string"
          }
        },
        "type": "object"
      },
      "name": "support_lifecycle",
      "outputSchema": null
    },
    {
      "description": "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).",
      "inputSchema": {
        "additionalProperties": false,
        "properties": {
          "lens": {
            "description": "The target release lens.",
            "enum": [
              "761",
              "mas811",
              "mas90",
              "mas91",
              "mas92"
            ],
            "type": "string"
          },
          "source": {
            "description": "The Automation Script source — Jython or JavaScript, a WORKORDER Object launch point. Up to 64 KiB.",
            "maxLength": 65536,
            "minLength": 1,
            "type": "string"
          }
        },
        "required": [
          "source",
          "lens"
        ],
        "type": "object"
      },
      "name": "test_automation_script_evidence",
      "outputSchema": null
    },
    {
      "description": "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.",
      "inputSchema": {
        "additionalProperties": false,
        "properties": {
          "from": {
            "description": "Source release, e.g. \"8.11\".",
            "type": "string"
          },
          "phase": {
            "description": "Optional: BEFORE, DURING or AFTER.",
            "type": "string"
          },
          "to": {
            "description": "Target release, e.g. \"9.2\".",
            "type": "string"
          }
        },
        "required": [
          "from",
          "to"
        ],
        "type": "object"
      },
      "name": "upgrade_checklist",
      "outputSchema": null
    },
    {
      "description": "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/<from>/<to>.",
      "inputSchema": {
        "additionalProperties": false,
        "properties": {
          "from": {
            "description": "Source release: \"7.6.1\", \"8.11\", \"9.0\", \"9.1\".",
            "type": "string"
          },
          "to": {
            "description": "Target release: \"8.11\", \"9.0\", \"9.1\", \"9.2\".",
            "type": "string"
          }
        },
        "required": [
          "from",
          "to"
        ],
        "type": "object"
      },
      "name": "upgrade_plan",
      "outputSchema": null
    }
  ]
}

Verify it yourself

curl -s https://api.teppi.xyz/v1/evidence/sha256:446f16005c3a54d616db1b229784aba3aacc398d97aa05b46b3b1214c6178d9f | sha256sum