...
runtime_get_info and runtime_set_target collapse into a single runtime_connect(solution?, profile?).runtime_browse_uns → runtime_browse_object_model (the tool walks all 12 runtime roots, not just the P1-strict UNS).runtime_get_object_context → runtime_describe_object — and it absorbs the former runtime_find_by_iri via a new iri parameter.runtime_list_by_type → runtime_list_instances, now bounded with max_results + name_mask wildcard filter.max_* caps with a truncated flag on the response.runtime_list_derived_types dropped — redundant with runtime_describe_object's derivedTypes context block....
Checkbox label | Category | Covers | Bit |
|---|---|---|---|
Enable MCP for Runtime | Master | Gates every RuntimeMCP tool. | 0x0002 |
Enable UNS Tools | UNS |
| 0x04 |
Enable Alarm Tools | Alarm | Dedicated alarm-query tools only: | 0x08 |
Enable Historian Tools | Historian |
| 0x10 |
Enable Custom Tools | Custom | Solution-authored | 0x20 |
Category semantics. Categories are defined by the TOOL being invoked, not by the runtime_connect itself is gated only by the master; it is always available when the master is on so AI clients can bootstrap before any category is enabled-object namespace the path happens to address:
Alarm.* namespace (e.g., runtime_get_value("Alarm.TotalCount")) stays under Enable UNS Tools. Any runtime-object value read is UNS-category regardless of path.runtime_describe_object (reports whether a specific tag is currently in alarm state) is describing the tag — UNS data — and gates on Enable UNS Tools, not Enable Alarm Tools.runtime_get_active_alarms and runtime_query_alarm_history.AI Runtime provides 9 built-in platform tools + solution-authored custom tools, organized by function.
...
Version | Date | Changes |
|---|---|---|
1.2 (draft) | 2026-04-24 | Refreshed for 10.1.5.1. Tool catalog went to 9 platform tools + custom (was 7). Session bootstrap unified as |
1.1 | 2026-02 | 7 built-in tools; updated architecture diagram; added |
...