business-central-mcp

bc_list_companies

Read-only

Retrieve all company names in the current Business Central environment and identify the active one, so you can verify a target company exists before switching.

Instructions

List all companies available in the current Business Central environment. Returns an array of company names along with the currently active company name. Use this before bc_switch_company to verify the target company exists and to discover available companies.

This tool opens the BC Companies system page internally, reads all entries, and closes it. It does not affect your currently open pages or session state. No parameters are required.

Do NOT use this if you already know the company name -- call bc_switch_company directly. If you need to work with data in a specific company, use bc_switch_company followed by bc_open_page.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description	Default
`companies`	Yes
`currentCompany`	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": {
+    "companies": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "displayName": {
+            "type": "string"
+          },
+          "name": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "name",
+          "displayName"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "currentCompany": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "currentCompany",
+    "companies"
+  ],
+  "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 declare readOnlyHint=true and openWorldHint=false, but the description goes further by disclosing the internal mechanism (opens the BC Companies system page, reads entries, closes it) and guaranteeing it won't disturb the currently open pages or session state. That side-effect disclosure is exactly the behavioral context an agent needs before chaining calls.

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 return shape, then usage, then mechanism. It is slightly longer than necessary: the closing sentence ('If you need to work with data in a specific company, use bc_switch_company followed by bc_open_page') partially restates the DO-NOT guidance already given.

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, so return values need not be explained, and the description still summarizes the return (company names plus the active company). Combined with annotations covering the safety profile, the definition is complete for a zero-param, read-only listing 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?

The tool takes zero parameters and the description states 'No parameters are required', which is the correct baseline for a 0-param tool. There is nothing further to disambiguate, so it sits at the expected ceiling without adding special insight.

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 and resource ('List all companies available in the current Business Central environment') and clarifies scope with 'in the current Business Central environment' plus the return payload. It also names the sibling tool it complements (bc_switch_company), so the agent can place it relative to alternatives 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 an explicit when-to-use ('before bc_switch_company to verify the target company exists'), an explicit when-not ('Do NOT use this if you already know the company name'), and names the alternative path (bc_switch_company, then bc_open_page). Nothing is left to inference.

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

Deploy Server