business-central-mcp

bc_navigate

Read-only

Navigate to a record on an open Business Central list or document page by bookmark: select a row or drill down to its card/detail page.

Instructions

Navigates to a specific record on an open Business Central List or Document page using its bookmark. Supports two actions: "select" positions the cursor on a row without opening it, and "drill_down" opens the record in its Card/Document page. Requires a pageContextId from bc_open_page and a bookmark from row data returned by bc_open_page or bc_read_data.

Action "select" (default): Positions the cursor on the specified row. Does NOT open the record or return new data -- it only moves the selection. Note: bc_execute_action can target a row directly via its own bookmark/rowIndex parameters, so you usually do not need a separate select before an action like Delete.

Action "drill_down": Opens the record's detail page (e.g., drilling down from Customer List opens Customer Card, drilling down from Sales Orders opens Sales Order). Returns a NEW pageContextId for the opened Card/Document page with its full state. The original List page remains open. Remember to bc_close_page both pages when done.

Section targeting: Use section (e.g., "lines") to navigate within a Document page's subpage repeater. Omit it for the header/default repeater.

Do NOT use this for Card pages -- it only works on pages with repeater rows. Do NOT confuse "select" with "drill_down": select just moves the cursor, drill_down opens a new page. For field-level lookups (enumerating valid values for a related-table field), use bc_lookup, not this tool.

Examples:

Select a row: { "pageContextId": "abc", "bookmark": "XXXX", "action": "select" }
Drill down to Card: { "pageContextId": "abc", "bookmark": "XXXX", "action": "drill_down" }
Drill down from a document line: { "pageContextId": "abc", "bookmark": "XXXX", "action": "drill_down", "section": "lines" }

Input Schema

TableJSON Schema

Name	Required	Description
`action`	No	"select" moves cursor to row (default). "drill_down" opens the record detail page (returns new pageContextId). For field lookups use the bc_lookup tool.
`section`	No	Section containing the row (e.g., "lines" for document line items). Omit for header/default repeater.
`bookmark`	Yes	Row bookmark from bc_open_page or bc_read_data results identifying which record to navigate to.
`pageContextId`	Yes	Page context ID of the List or Document page containing the row to navigate to.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`pageType`	No
`sections`	No
`dialogsOpened`	Yes
`changedSections`	Yes
`targetPageContextId`	No
`requiresDialogResponse`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv2.0.0Oct 15, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "additionalProperties": false,
+  "properties": {
+    "changedSections": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "dialogsOpened": {
+      "items": {
+        "additionalProperties": {},
+        "properties": {
+          "formId": {
+            "type": "string"
+          },
+          "message": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "formId"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "pageType": {
+      "type": "string"
+    },
+    "requiresDialogResponse": {
+      "type": "boolean"
+    },
+    "sections": {
+      "items": {
+        "additionalProperties": {},
+        "properties": {},
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "targetPageContextId": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "changedSections",
+    "dialogsOpened",
+    "requiresDialogResponse"
+  ],
+  "type": "object"
+}

First observedv1.5.0Jul 29, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations only declare readOnlyHint and openWorldHint, so the description carries the real behavioral load: select moves the cursor without returning data, drill_down returns a NEW pageContextId while the original List page stays open, and both pages must later be closed via bc_close_page. That page-lifecycle disclosure is valuable context beyond the annotations, though error cases (stale pageContextId, invalid bookmark) go unmentioned.

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?

Front-loaded with purpose and the two actions before detail, then section targeting, exclusions, and examples in a scannable order. It runs long and the select-vs-drill_down distinction is restated twice, but every section still earns its place for an agent choosing between navigation modes.

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?

An output schema exists, yet the description still adds the one return fact an agent must act on (a new pageContextId for the opened page) and the cleanup obligation that spans two tools. Combined with the section/action coverage, an agent has everything needed to invoke and follow up correctly.

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 baseline is 3, but the description adds provenance and usage meaning: pageContextId must come from bc_open_page, bookmark from bc_open_page/bc_read_data, and section is for a Document page's subpage repeater with omission meaning header/default. The three concrete invocation examples map parameter combinations to real scenarios, which the schema alone does not convey.

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?

States a specific verb (navigates) and resource (record on a Business Central List/Document page) plus the exact mechanism (bookmark) and the two supported actions. It explicitly differentiates itself from siblings bc_lookup, bc_execute_action, and Card pages, so an agent can route without opening a schema.

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?

Gives explicit when-to-use (row selection vs. opening a detail page), when-not (Card pages, field lookups), and names the alternative tools (bc_lookup, bc_execute_action) with the conditions that select them. The note that a separate select is usually unnecessary before an action is exactly the kind of routing guidance that prevents misuse.

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

Deploy Server