Skip to main content
Glama

reference_tree

Read-only

Inspect a hierarchical structure of references for Dynamics 365 Finance and Operations X++ artifacts by package, model, artifact type, artifact, and member, with parent, limit, and offset paging.

Instructions

Inspect the reference tree by package, model, artifact type, artifact, and member.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "reference_tree"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
offsetNo
parentNo

Output Schema

NameRequiredDescriptionDefault
okYes
errorNo
itemsNo
limitYes
totalYes
offsetYes
freshnessNo
truncatedYes
nextOffsetYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.16.0

TDQS

C2.2/5.0
Behavior2/5

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

Annotations already declare readOnlyHint and openWorldHint, so safety is covered. The description adds nothing beyond that: it does not mention that results are paginated, what the tree hierarchy actually is, or what "open world" means here (e.g., filesystem/workspace resolution).

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

Conciseness3/5

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

A single short sentence with no padding, so nothing is wasted, but it is under-specified rather than concise. The listed dimensions are front-loaded but do not map to anything actionable.

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

Completeness2/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 described. However, the three input parameters are undocumented in both schema and description, and the tree's structure is never explained, leaving the agent unable to call this correctly.

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

Parameters1/5

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

Schema description coverage is 0% for three parameters (limit, offset, parent), so the description must compensate and does not. Worse, it names five concepts that are not parameters at all while omitting limit, offset, and parent entirely, actively misdirecting the agent about what can be supplied.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The verb "Inspect" and resource "reference tree" are stated, but "reference tree" is undefined jargon and the enumerated dimensions (package, model, artifact type, artifact, member) read like filters even though none exist as parameters. An agent cannot tell from this sentence how it differs from siblings such as reference_graph or reference_resolve.

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?

There is no guidance on when to use this versus the many reference_* and ide_* siblings, no prerequisites, and no exclusions. The agent must infer usage purely from the tool name.

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