Skip to main content
Glama
MehrozeKhan73

Business Central MCP Server

bc_navigate

Navigate to a record in an open Business Central list or document page using its bookmark. Use 'select' to position the cursor or 'drill_down' to open the record's 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
NameRequiredDescriptionDefault
actionNo"select" moves cursor to row (default). "drill_down" opens the record detail page (returns new pageContextId). For field lookups use the bc_lookup tool.
sectionNoSection containing the row (e.g., "lines" for document line items). Omit for header/default repeater.
bookmarkYesRow bookmark from bc_open_page or bc_read_data results identifying which record to navigate to.
pageContextIdYesPage context ID of the List or Document page containing the row to navigate to.
Behavior5/5

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

The description fully discloses behavioral traits: 'select' only moves cursor, does not return data; 'drill_down' opens a new page and returns a new pageContextId; both pages must be closed. No annotations provided, so description carries the full burden.

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?

The description is well-organized with a summary, action breakdown, additional notes, and examples. It is slightly long but every sentence is informative. Could be more concise, but remains effective.

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?

The description covers prerequisites, action behaviors, return values (for drill_down), section targeting, and post-usage cleanup. It also differentiates from sibling tools, making it complete for the complexity of this tool.

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%, but the description adds significant value by explaining the context and effects of each parameter, such as the action enum meanings, section targeting, and the role of pageContextId/bookmark in the workflow.

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 clearly states the tool's purpose: navigating to a specific record on a Business Central List or Document page using its bookmark. It defines two actions, 'select' and 'drill_down', and distinguishes from sibling tools like bc_lookup and bc_execute_action.

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?

The description provides explicit guidance on when to use the tool (e.g., not for Card pages, not for field lookups), when to use alternatives (bc_lookup for lookups, bc_execute_action for actions), and includes examples for clarity.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/MehrozeKhan73/Business-Central-MCP-Integration'

If you have feedback or need assistance with the MCP directory API, please join our Discord server