Skip to main content
Glama
Sign In
bc-source-mcp

bc-source-mcp

by glachana
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Get event publishers of an AL object

bc_get_event_publishers
Read-onlyIdempotent

Lists all event publishers (IntegrationEvent, BusinessEvent, InternalEvent) in a given AL object, with name, kind, signature, attribute, and source line. Useful for finding events to subscribe to.

Instructions

Lists all event publishers ([IntegrationEvent], [BusinessEvent], [InternalEvent]) defined inside a specific AL object. Returns the event name, kind, full procedure signature, attribute, and source line. Useful for finding events to subscribe to.

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": {
      "branch": "<branch>",
      "source_type": "<source_type>",
      "source_name": "<source_name>"
    },
    "name": "bc_get_event_publishers"
  }
}

Input Schema

NameRequiredDescriptionDefault
branchYesBranch name, e.g. "w1-26"
source_typeYesContainer object type (typically "codeunit", but can be "table", "page", etc.)
source_nameYesContainer object name, e.g. "Approvals Mgmt." (without quotes)

Output Schema

NameRequiredDescriptionDefault
branchYes
source_typeYes
source_nameYes
totalYes
eventsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already indicate safe, idempotent, and open-world behavior. The description adds value by detailing what exactly is listed (event name, kind, procedure signature, attribute, source line) and the types of events, going beyond 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?

The description is two sentences long, front-loaded with the main action and output, followed by a use case. Every word is necessary, with no redundancy or filler.

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?

Given the presence of an output schema and comprehensive annotations, the description is complete: it explains the tool's purpose, what it returns, and when to use it. No gaps are evident.

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 coverage is 100%, so the schema already documents parameters. The description adds context by linking parameters to 'a specific AL object,' but does not elaborate on individual parameters. Baseline is appropriate.

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 lists event publishers defined inside a specific AL object, specifying the verb 'lists' and the resource. It also details the output fields, making the purpose unmistakable and distinct from sibling tools.

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

Usage Guidelines4/5

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

The description includes 'Useful for finding events to subscribe to,' which provides clear context for when to use this tool. It does not explicitly exclude alternatives, but the context is sufficient.

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

Deploy Server

Other Tools