bc-source-mcp

Overview Schema Source Related Servers Discussions Admin

Find an object across indexed branches

bc_find_object_across_branches

Read-onlyIdempotent

Search for an AL object by type and exact name across indexed branches to compare its presence or path in different versions or localizations.

Instructions

Searches for an AL object (by type and exact name) across all branches that have already been indexed in this MCP instance. Use this to compare presence/path of an object across versions or localizations. Does not trigger indexing — call bc_list_apps on a branch first if you want to include it.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "type": "<type>",
      "name": "<name>"
    },
    "name": "bc_find_object_across_branches"
  }
}

Input Schema

Name	Required	Description
`type`	Yes	AL object type (table, page, codeunit, ...)
`name`	Yes	Exact object name
`branches`	No	Optional list of branches to restrict the search to (e.g. ["w1-26", "fr-26"]). If omitted, searches all indexed branches.

Output Schema

Name	Required	Description	Default
`type`	Yes
`name`	Yes
`total`	Yes
`results`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.1Jun 18, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already provide readOnlyHint and idempotentHint, so the description adds value by clarifying that indexing is not triggered, which is important context beyond the annotations.

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

Conciseness5/5

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

Two sentences, front-loaded with purpose and a clear usage guideline. No extraneous words.

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 read-only, idempotent search tool with full schema descriptions and an output schema, the description covers purpose, usage, and the key behavioral note about indexing. Complete.

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

Parameters3/5

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

Schema description coverage is 100%, so the baseline is 3. The description adds minimal extra meaning beyond what the schema already provides for each parameter.

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 searches for an AL object by type and exact name across indexed branches, distinguishing it from siblings like bc_get_object (retrieves single object) and bc_list_objects (lists objects in a branch).

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?

Explicitly states when to use ('compare presence/path of an object across versions or localizations') and what not to assume ('Does not trigger indexing — call bc_list_apps on a branch first if you want to include it').

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

Deploy Server