Skip to main content
Glama
glachana

bc-source-mcp

by glachana

List objects in a branch

bc_list_objects
Read-onlyIdempotent

List AL objects in a Business Central branch, filtering by object type, app, or name pattern with wildcards.

Instructions

Lists AL objects in a branch, with optional filters by type, app, and name pattern. Use "*" as wildcard in name_pattern (translated to SQL LIKE %). Triggers indexing on first use of a branch.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
branchYesBranch name, e.g. "w1-26"
typeNoAL object type filter (table, page, codeunit, report, enum, query, xmlport, tableextension, pageextension, etc.)
appNoApp name filter (exact match), e.g. "Base Application"
name_patternNoName pattern with * wildcards, e.g. "Sales*", "*Header*"
limitNoMax items to return. Default 100.
offsetNoPagination offset. Default 0.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
branchYes
totalYes
offsetYes
limitYes
itemsYes
Behavior4/5

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

The description adds the important behavioral note: 'Triggers indexing on first use of a branch.' This goes beyond the annotations (readOnlyHint, idempotentHint, openWorldHint) and informs the agent of a side effect.

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?

The description is concise, starting with the main purpose and then adding key details in two additional sentences. No unnecessary words.

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

Completeness4/5

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

Given the tool's complexity (6 parameters, output schema exists), the description covers the main functionality and a critical side effect (indexing). It could mention pagination defaults but those are in the schema. Overall it provides sufficient context.

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% with parameter descriptions, but the description adds value by explaining the wildcard behavior: 'Use "*" as wildcard in name_pattern (translated to SQL LIKE %).' This clarifies usage beyond the schema.

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 verb 'Lists' and the resource 'AL objects in a branch', and mentions optional filters. This distinguishes it from siblings like bc_find_object_across_branches which searches across branches.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives like bc_find_object_across_branches or bc_get_object. The description only states what the tool does, not when it is appropriate.

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/glachana/bc-source-mcp'

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