business-central-mcp

bc_wizard_navigate

Destructive

Advance, return, finish, or cancel a multi-step Business Central wizard (NavigatePage) during setup; use it after opening the modal page to move through steps and complete the flow.

Instructions

Drive a Business Central NavigatePage / wizard by semantic step. Use after bc_open_page on a page whose response has isModal: true and pageType: "NavigatePage" (Continia activation wizards, BC setup wizards, request pages with multi-step layouts). The action argument is one of: "next" (advance), "back" (return to previous step), "finish" (complete the wizard), "cancel" (abort).

bc-mcp identifies the navigation buttons by the icon resource BC's own client uses (Actions/PreviousRecord, Actions/NextRecord, Actions/Approve), not by SystemAction or caption -- so localised wizards work without changes. The response surfaces fields visible on the new step, the remaining navigation options (availableNav), and a closed flag set when the wizard finished.

Typical workflow: bc_open_page (returns isModal=true, fields for step 0) -> bc_write_data (fill step 0 inputs) -> bc_wizard_navigate { action: "next" } -> bc_write_data (fill step 1) -> ... -> bc_wizard_navigate { action: "finish" }. The wizard closes itself on finish/cancel; the pageContextId becomes invalid afterwards. A step that opens a separate dialog (e.g. "Set up SMTP Account") returns it in dialogsOpened with its own pageContextId: fill it with bc_write_data against that id and answer it with bc_respond_dialog, not through the wizard's pageContextId.

Do NOT use this for non-wizard pages -- use bc_execute_action instead. Do NOT call "next" past the last step -- use "finish" once availableNav lists it.

Example: { "pageContextId": "abc", "action": "next" }

If the action produces a file (Open in Excel, Print, export), its bytes appear in downloads[] (an operationId replay returns the metadata with error code NOT_REPLAYED instead of the bytes); links BC would open externally appear in externalUris[] and are never fetched by the server.

Input Schema

Name	Required	Description
`action`	Yes	Wizard step navigation. "next" advances, "back" returns to previous step, "finish" completes the wizard, "cancel" aborts.
`operationId`	No	Optional idempotency key (e.g. a UUID you generate). Retrying with the same operationId and the same arguments returns the first call's stored result instead of running the change again, so a retry after a dropped connection or timeout cannot double-post. Reusing it with different arguments is rejected (OPERATION_ID_REUSED). If the first call's outcome is unknown, the retry returns OPERATION_IN_DOUBT: check the record's state before acting again under a new operationId. Every result of this tool carries replaySafe: true means BC's response proved that re-running the same call (even under a new operationId, after an unknown outcome) cannot apply the change twice -- the write was echoed as an absolute value, or the form it acted on is closed so BC rejects a re-run; false means a re-run may double-apply or nothing proved otherwise, so read the record back before retrying. Replay is time-limited: a completed entry is kept for BC_OPERATION_TTL (default 24h), after which the same operationId runs the call again; check with bc_get_operation before a late retry. A replayed result carries download metadata (fileName, contentType, sizeBytes, savedPath) but not the file bytes.
`pageContextId`	Yes	Page context ID returned by bc_open_page for a NavigatePage / wizard.

Output Schema

Name	Required	Description	Default
`closed`	Yes
`fields`	Yes
`caption`	Yes
`success`	Yes
`downloads`	Yes
`replaySafe`	Yes
`availableNav`	Yes
`externalUris`	Yes
`dialogsOpened`	Yes
`changedSections`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv2.4.7Nov 5, 2026
- addedOutput schema / properties / dialogsOpened / items / properties / pageContextId
```
Added value: +{
+  "type": "string"
+}
```
- changedOutput schema / properties / dialogsOpened / items / required
```
Previous value: -[
-  "formId"
-]New value: +[
+  "formId",
+  "pageContextId"
+]
```

Changed2 schema fields changedv2.0.0Oct 15, 2026

addedInput schema / properties / operationId

Added value: +{
+  "description": "Optional idempotency key (e.g. a UUID you generate). Retrying with the same operationId and the same arguments returns the first call's stored result instead of running the change again, so a retry after a dropped connection or timeout cannot double-post. Reusing it with different arguments is rejected (OPERATION_ID_REUSED). If the first call's outcome is unknown, the retry returns OPERATION_IN_DOUBT: check the record's state before acting again under a new operationId. Every result of this tool carries replaySafe: true means BC's response proved that re-running the same call (even under a new operationId, after an unknown outcome) cannot apply the change twice -- the write was echoed as an absolute value, or the form it acted on is closed so BC rejects a re-run; false means a re-run may double-apply or nothing proved otherwise, so read the record back before retrying. Replay is time-limited: a completed entry is kept for BC_OPERATION_TTL (default 24h), after which the same operationId runs the call again; check with bc_get_operation before a late retry. A replayed result carries download metadata (fileName, contentType, sizeBytes, savedPath) but not the file bytes.",
+  "maxLength": 200,
+  "minLength": 1,
+  "type": "string"
+}

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "additionalProperties": false,
+  "properties": {
+    "availableNav": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "caption": {
+      "type": "string"
+    },
+    "changedSections": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "closed": {
+      "type": "boolean"
+    },
+    "dialogsOpened": {
+      "items": {
+        "additionalProperties": {},
+        "properties": {
+          "formId": {
+            "type": "string"
+          },
+          "message": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "formId"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "downloads": {
+      "items": {
+        "additionalProperties": {},
+        "properties": {
+          "contentType": {
+            "type": "string"
+          },
+          "fileName": {
+            "type": "string"
+          },
+          "savedPath": {
+            "type": "string"
+          },
+          "sizeBytes": {
+            "type": "number"
+          },
+          "style": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "fileName",
+          "contentType",
+          "sizeBytes",
+          "style"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "externalUris": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "style": {
+            "type": "string"
+          },
+          "uri": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "uri",
+          "style"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "fields": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "editable": {
+            "type": "boolean"
+          },
+          "name": {
+            "type": "string"
+          },
+          "value": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "name",
+          "editable"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "replaySafe": {
+      "type": "boolean"
+    },
+    "success": {
+      "type": "boolean"
+    }
+  },
+  "required": [
+    "success",
+    "caption",
+    "fields",
+    "availableNav",
+    "closed",
+    "changedSections",
+    "dialogsOpened",
+    "downloads",
+    "externalUris",
+    "replaySafe"
+  ],
+  "type": "object"
+}

First observedv1.5.0Jul 29, 2026

TDQS

A4.8/5.0

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already flag destructiveHint=true and idempotentHint=false, and the description corroborates this by stating the wizard closes itself on finish/cancel and the pageContextId becomes invalid afterwards. It adds genuinely non-obvious behavior: buttons are located by BC's own icon resources (Actions/PreviousRecord, Actions/NextRecord, Actions/Approve) so localized wizards work, the response surfaces new-step fields, availableNav and a closed flag, and side outputs land in downloads[]/externalUris[] with NOT_REPLAYED on replay.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Structure is strongly front-loaded: purpose and precondition first, action semantics second, workflow third, exclusions fourth, example last. A few sentences are redundant with the schema (the action enum restatement) and the downloads/externalUris paragraph is only loosely tied to navigation, keeping it out of the top band despite overall efficiency.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a stateful, multi-step, destructive-by-closure tool, the description covers entry conditions, step loop, termination, invalidated context, nested dialogs, and side-effect channels. An output schema exists, yet the extra return-shape detail (availableNav, closed, dialogsOpened) is additive rather than filler.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the enum values for action and the operationId idempotency contract are already documented in the schema. The description still adds sequencing meaning beyond the enum: which action is legal at which point in the flow, plus a concrete invocation example. It does restate the action meanings already present in the schema, which caps it below a 5.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb and resource (navigate a Business Central NavigatePage/wizard by semantic step) and pins the exact precondition: a page opened via bc_open_page returning isModal: true and pageType: "NavigatePage". It also explicitly disclaims the sibling case, telling the agent this is not for non-wizard pages and to use bc_execute_action there.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives a full when-to-use rule (after bc_open_page on a NavigatePage), a when-not-to-use rule (non-wizard pages → bc_execute_action), an intra-tool constraint (do NOT call "next" past the last step; use "finish" once availableNav lists it), and a routing rule for nested dialogs (bc_respond_dialog against the child pageContextId, not the wizard's). The end-to-end workflow with bc_write_data interleaved makes the sequencing unambiguous.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.