Skip to main content
Glama

reference_extensions

Read-only

Lists extension elements, chain-of-command classes, event handlers, and delegate subscribers that hook into a Dynamics 365 X++ artifact or member, so you can see dependencies before changes.

Instructions

List what extends an artifact: its extension elements (TableExtension, FormExtension, EnumExtension... named .), chain-of-command classes ([ExtensionOf]), event handlers ([DataEventHandler], [FormEventHandler], [FormDataSourceEventHandler], [FormControlEventHandler], [FormDataFieldEventHandler], [PreHandlerFor], [PostHandlerFor]) and delegate subscribers ([SubscribesTo]) that name the artifact or one of its members. Use it before changing an artifact to see the code that hooks into 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": {
      "id": "<id>"
    },
    "name": "reference_extensions"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesArtifact or member id, e.g. /Tables/CustTable or /Forms/CustTable/DataSources/CustTable
limitNo

Output Schema

NameRequiredDescriptionDefault
idNo
okYes
errorNo
elementsNo
extendersNo
freshnessNo
truncatedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.16.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations cover the safety profile (readOnlyHint, openWorldHint) and an output schema exists, so the description's added value is the result composition: what forms of extension are matched and the naming markers used to identify them ([ExtensionOf], [SubscribesTo], the handler attributes). It does not disclose pagination/truncation behavior tied to the limit parameter, leaving one behavioral gap.

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?

Two sentences, front-loaded with the core action, then the usage cue. The parenthetical list of attribute names is long but each item is load-bearing for recognizing results; no filler or restatement of the name.

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?

For a read-only lookup with an output schema already defining return shape, the description supplies enough: scope of matching, result categories, and a decision cue. The only omission is how the limit interacts with results (truncation vs. paging), which matters slightly at up to 1000 entries.

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?

The id parameter already has a schema description, but the prose adds meaning by clarifying it matches the artifact OR one of its members, implying member-path IDs are valid. The limit parameter (1-1000, default 200) is undocumented in both description and schema, so half the parameters remain semantically opaque; baseline 3 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?

Specific verb 'List' plus a precisely scoped resource: things that extend an artifact, broken into four named categories (extension elements, chain-of-command classes, event handler attributes, delegate subscribers). The enumeration of concrete attribute/suffix markers distinguishes it from graph/references siblings at a glance.

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?

Gives an explicit use case: 'Use it before changing an artifact to see the code that hooks into it,' which tells the agent exactly when this tool is the right call. It does not name an alternative (e.g. reference_references or ide_references) or state when not to use it, so it falls short of a 5.

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