--- sourceDocument: Australia Enterprise Architecture sourceDocumentLink: https://www.servicenow.com/docs/r/australia/application-portfolio-management Release : - australia ft:locale : - en-US ft:publication_title : - Australia Enterprise Architecture ft:clusterId : - appportman bundleId : - appportman workflow : - Technology --- # Tool parameters # MCP for Enterprise Architecture tool parameters {#ariaid-title1} Release version: Australia Updated September 23, 2026 ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 5 minutes to read Summarize ![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete. ## Summary of MCP for Enterprise Architecture Tool Parameters This document details the parameters accepted by various MCP for Enterprise Architecture (EA) tools within ServiceNow's Australia release. These tools are designed to retrieve and analyze EA data without modifying records in your instance. They support pagination and provide structured insights into business applications, capabilities, and related architectural elements. Show full answer Show less ## Key Parameters and Their Practical Use * **Get EA Business App Insights:** Enables generation of tailored insights for business applications, such as lifecycle, technical health, and strategic alignment. Parameters like **sysid** specify the application, while **pagecontext** shapes the insight type (e.g., business portfolio or app rationalization). * **Capability Hierarchy App Resolver:** Supports querying applications mapped to business capabilities through modes like direct mapping, hierarchy, or health assessments. Requires capability identification and optionally scopes results by fiscal periods and trends. * **App Rationalization Query:** Facilitates complex queries on application and capability scores, risk assessments, and rationalization classifications. Requires specifying the operation type, entity type, and relevant arguments, allowing you to analyze performance and prioritize investments. * **Related Entities Resolver:** Identifies and analyzes relationships between entities such as applications and services. Modes cover direct and indirect relationships, counts, and multi-level impact analysis, with parameters controlling traversal depth and result filtering. * **Artifact Resolver:** Retrieves architectural artifacts linked to entities or vice versa, aiding in documentation and impact analysis. Parameters include entity names, tables, and pagination controls to manage result sets. * **Diagram Change Analysis:** Available with the Enterprise Modeling and Visualization plugin, this tool compares diagram versions or summarizes a single diagram, highlighting changes and business impacts. Parameters define the diagrams, comparison modes, and output detail levels. ## Why This Matters Understanding and correctly using these parameters allows ServiceNow customers to effectively leverage MCP for Enterprise Architecture tools to gain actionable insights. These insights support portfolio management, application rationalization, impact analysis, and architectural documentation without altering core data, ensuring safe and informed decision-making. ## What to Expect * Accurate retrieval of business application and capability data aligned with your organizational context. * Customized insights shaped by prompt variants and scoped to specific fiscal periods or capabilities. * Comprehensive relationship and impact analyses across your enterprise architecture. * Support for pagination and detailed trend analysis to handle large data sets effectively. * Integration with visualization tools for diagram comparisons and change impact summaries. Parameters that each MCP for Enterprise Architecture tool accepts, and how to phrase prompts that return the data you need. The tools installed with the application are annotated as read-only. They retrieve or analyze EA data but don't create, update, or delete records in your instance. For details about tool annotations, see [Components installed with MCP for Enterprise Architecture](https://www.servicenow.com/docs/SiK3R0bRhlMsttC1yPEGNQ "When you install the MCP for Enterprise Architecture plugin, these tools, scripted REST APIs, and access controls are added to your instance."). Tools that return lists support pagination through the limit and offset parameters. When more results are available, the response includes `has_more` and `next_offset` values that the AI assistant uses to request the next set of results. ## Get EA Business App Insights {#ea-mcp-server-tool-parameters__section_ea_mcp_param_app_insights} {#ea-mcp-server-tool-parameters__table_ea_mcp_param_app_insights__entry__2} | Parameter | Description | |-|-| | sys_id | Sys ID of the business application to generate insights for. Required. | | page_context | Prompt variant that shapes the insights. Possible values: * `business_portfolio`: Capability mapping and business value of the application. * `app_rationalization_list`: Consolidation, redundancy, and modernization recommendations. * `app_rationalization_bubble_chart`: Technical fitness compared with business value, for investment prioritization. {#ea-mcp-server-tool-parameters__ul_ea_mcp_param_page_context} When omitted, general insights covering lifecycle, technical health, cost, risk, and strategic alignment are generated. | | primary_capability_sys_id | Sys ID of the business capability to treat as the primary capability. Used only when page_context is `business_portfolio`. When omitted, the first capability connected to the application is used. | | bubble_chart_axis | Sys ID of the bubble chart axis configuration (`apm_bubble_chart` record) to use. Used only when page_context is `app_rationalization_bubble_chart`. | | fiscal_period | Sys ID of the fiscal period (`fiscal_period` record) to scope indicator scores to. | [Table 1. Get EA Business App Insights parameters] {#ea-mcp-server-tool-parameters__table_ea_mcp_param_app_insights} ## Capability Hierarchy App Resolver {#ea-mcp-server-tool-parameters__section_ea_mcp_param_cap_hierarchy} {#ea-mcp-server-tool-parameters__table_ea_mcp_param_cap_hierarchy__entry__2} | Parameter | Description | |-|-| | mode | Operation to perform. Possible values: * `prompt`: Hierarchy statistics for a capability, before applications are queried. * `direct`: Applications mapped directly to the capability. * `hierarchy`: Applications mapped to the capability and all its descendant capabilities. * `all_top_level`: Portfolio-wide coverage across all top-level capability domains. * `bc_health`: Overall score, indicator scores, assessment status, health of supporting business applications, and an optional multi-year trend. * `resolve_capability`: Sys ID of a capability, matched by name. * `get_descendants`: All descendant capabilities of a capability. {#ea-mcp-server-tool-parameters__ul_ea_mcp_param_cap_mode} Required. | | capability_name | Name of the business capability. Required for all modes except `all_top_level`. If no exact match is found, the closest matches are returned. | | target_table | Table of the entities to look up. Used in the `direct`, `hierarchy`, and `all_top_level` modes. Default: `cmdb_ci_business_app` | | fiscal_period_name | Fiscal period for the `bc_health` mode, for example, FY25. When omitted, the current fiscal year is used. | | include_trend | Option to include multi-year trend history in the `bc_health` mode. Default: false | | trend_period_count | Number of historical fiscal years in the trend, up to 20. Used only when include_trend is true. Default: 5 | | limit, offset | Pagination controls. Default: 100 records, starting at offset 0 | [Table 2. Capability Hierarchy App Resolver parameters] {#ea-mcp-server-tool-parameters__table_ea_mcp_param_cap_hierarchy} ## App Rationalization Query {#ea-mcp-server-tool-parameters__section_ea_mcp_param_app_rat} {#ea-mcp-server-tool-parameters__table_ea_mcp_param_app_rat__entry__2} | Parameter | Description | |-|-| | operation | Query to run. Possible values: * `RESOLVE_ENTITY`, `RESOLVE_FISCAL_PERIOD`, `RESOLVE_INDICATOR`: Sys ID of an entity, fiscal period, or indicator, matched by name. * `LIST_INDICATORS_FOR_ENTITY`: Indicators that apply to an entity. * `GET_OVERALL_SCORE`, `GET_INDICATOR_SCORE`, `GET_FULL_SCORECARD`: Overall score, a single indicator score, or all indicator scores for an entity. * `FILTER_ENTITIES_BY_CRITERIA`: Entities that meet one or more score conditions. * `COMPARE_PERIODS`: Score trend across fiscal periods. * `CLASSIFY_QUADRANT`: Rationalization quadrant (invest, sustain, migrate, or retire) based on two indicators. * `SCORE_DISTRIBUTION`: Portfolio-wide distribution of an indicator or overall score. * `GET_TPM_RISK`, `FILTER_BY_TPM_RISK`: TLM technology risk score for an entity, or entities above or below a risk threshold. {#ea-mcp-server-tool-parameters__ul_ea_mcp_param_app_rat_ops} Required. | | entity_type | Type of entity to query. For score operations: `business_app` or `business_capability`. For technology risk operations: `business_app`, `service`, `hardware_product_model`, or `software_product`. Required for all operations except `RESOLVE_FISCAL_PERIOD` and `RESOLVE_INDICATOR`. | | op_args | Operation-specific arguments, such as the entity name, indicator names, score conditions, or fiscal periods to compare. Required. | | global_opts | Optional settings that apply to all operations: the fiscal period to score against, pagination (default 200 records, maximum 500), and whether to include entity names in the results. | [Table 3. App Rationalization Query parameters] {#ea-mcp-server-tool-parameters__table_ea_mcp_param_app_rat} ## Related Entities Resolver {#ea-mcp-server-tool-parameters__section_ea_mcp_param_rel_entities} {#ea-mcp-server-tool-parameters__table_ea_mcp_param_rel_entities__entry__2} | Parameter | Description | |-|-| | mode | Analysis to perform. Possible values: * `related`: Entities directly related to the source entities. * `list_related`: Full list of source and target pairs, with statistics. * `not_related`: Source entities that have no relationship to the target type, for example, applications without any service. * `not_related_multi_hop`: Source entities with no indirect relationship through a path of two or three tables, for example, applications without servers through their services. * `counts_only`: Relationship counts and statistics per source entity, for example, applications with more than three services. * `traverse`: Multi-level impact or dependency analysis from a single configuration item (CI), for example, what depends on a database. {#ea-mcp-server-tool-parameters__ul_ea_mcp_param_rel_mode} Required. | | source_table, target_table | Tables of the source and target entities, which must be directly related through CI relationships. Required for all modes except `not_related_multi_hop` and `traverse`. | | source_names | Names of up to 50 source entities to restrict the query to. | | rel_type_sys_id | Sys ID of a relationship type, used when more than one relationship type exists between the same two tables. | | path | Two or three table names, from source to target, for the `not_related_multi_hop` mode. | | ci_name, ci_sys_id | Name or sys ID of the CI to start from, for the `traverse` mode. A name that matches more than one CI returns the candidates to choose from. | | direction | Direction of the `traverse` analysis. Possible values: * `up`: What depends on the CI (impact analysis). * `down`: What the CI depends on. * `both`: Both directions. {#ea-mcp-server-tool-parameters__ul_ea_mcp_param_rel_direction} Default: up | | max_levels | Number of relationship levels to traverse, up to 10. Default: 6 | | max_nodes | Number of CIs to discover during traversal, up to 500. When the limit is reached before all levels are traversed, the response indicates that the results may be partial. Default: 250 | | target_class | CI class to filter traversal results to, for example, `cmdb_ci_business_capability`. | | include_paths | Option to include the relationship path from each discovered CI back to the starting CI. Default: true | | include_svc_assoc | Option to also traverse service-to-CI associations, in addition to CI relationships. Default: false | | limit, offset | Pagination controls. Default: 100 records (`counts_only` mode: up to 5,000; `traverse` mode: 10, up to 30), starting at offset 0 | [Table 4. Related Entities Resolver parameters] {#ea-mcp-server-tool-parameters__table_ea_mcp_param_rel_entities} ## Artifact Resolver {#ea-mcp-server-tool-parameters__section_ea_mcp_param_artifact} {#ea-mcp-server-tool-parameters__table_ea_mcp_param_artifact__entry__2} | Parameter | Description | |-|-| | mode | Lookup to perform. Possible values: * `artifacts_for_entity`: Architectural artifacts, such as documents and diagrams, linked to an entity. * `entities_for_artifact`: Entities that an architectural artifact documents. * `all_for_table`: Entity-to-artifact mapping for all entities in a table. {#ea-mcp-server-tool-parameters__ul_ea_mcp_param_artifact_mode} Default: artifacts_for_entity | | entity_name | Name of the entity (`artifacts_for_entity` mode) or of the architectural artifact (`entities_for_artifact` mode). Not used in the `all_for_table` mode. | | entity_table | Table of the entities to look up. Possible values: `cmdb_ci_business_app`, `cmdb_ci_service`, `cmdb_ci_business_capability`, `cmdb_ci_information_object`, `cmdb_ci_appl`, or `cmdb_ci_business_service`. Required for the `artifacts_for_entity` and `all_for_table` modes. | | limit, offset | Pagination controls. Default: 10 records, up to 30, starting at offset 0 | [Table 5. Artifact Resolver parameters] {#ea-mcp-server-tool-parameters__table_ea_mcp_param_artifact} ## Diagram change analysis {#ea-mcp-server-tool-parameters__section_ea_mcp_param_diagram} This tool is available only when the Enterprise Modeling and Visualization plugin (com.snc.apm_modelling_tool) is installed on your instance. {#ea-mcp-server-tool-parameters__table_ea_mcp_param_diagram__entry__2} | Parameter | Description | |-|-| | action_type | Analysis to perform. Possible values: * `summary`: Structured overview of a single diagram, identifying the central business application and its connected entities. * `compare`: Comparison of two diagram versions, with the added, removed, and modified elements and a business-impact summary. {#ea-mcp-server-tool-parameters__ul_ea_mcp_param_diagram_action} Default: compare | | diagram_version_a | Sys ID of the diagram instance to summarize, or of the baseline version when comparing. Required. | | diagram_version_b | Sys ID of the updated diagram version to compare against the baseline. Required for the `compare` action. | | diagram_type | Type of diagram. Possible values: Business Hierarchy Map, Business Capability Map, or Business Process Map. Default: Business Hierarchy Map | | output_granularity_level | Level of detail in the comparison output. Possible values: `executive` (business summary) or `high` (detailed). Default: executive | [Table 6. Diagram change analysis parameters] {#ea-mcp-server-tool-parameters__table_ea_mcp_param_diagram}