Skip to main content
Glama

pbi_trace_measure_end_to_end

Trace a DAX measure end-to-end across Dependent Measures -> Model Columns & Tables -> Power Query M Steps -> Upstream Dataflows (Gen1/Gen2) -> Native SQL & Physical Sources, returning Markdown documentation or structured JSON.

Instructions

Trace a DAX measure end-to-end across Dependent Measures -> Model Columns & Tables -> Power Query M Steps -> Upstream Dataflows (Gen1/Gen2) -> Native SQL & Physical Sources, returning Markdown documentation or structured JSON.

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": {
      "measure": "<measure>"
    },
    "name": "pbi_trace_measure_end_to_end"
  }
}

Input Schema

NameRequiredDescriptionDefault
modelNoOptional semantic model name or dataset GUID filter.
formatNoOutput format: 'markdown' (default, audit-ready KPI spec) or 'json' (nodes + edges).
measureYesDAX measure name or Table[Measure] reference.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.1.0

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. It usefully discloses that the trace spans dataflow generations (Gen1/Gen2) and physical SQL sources and that output can be audit-ready Markdown or a nodes+edges JSON graph, but it says nothing about connection/permission prerequisites, cost or latency of a deep trace, or failure behavior when a measure or upstream source cannot be resolved.

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?

It is a single front-loaded sentence that leads with the verb and resource, then uses an arrow chain to convey traversal order compactly. Dense but every clause carries information; no filler or repetition.

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

Completeness3/5

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

With no annotations and no output schema, the description must cover behavioral and return-shape context itself. It does describe the two output formats and the traversal depth, but omits prerequisites and what happens with large or unresolvable lineage graphs, leaving gaps for a multi-hop trace tool.

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 all three parameters are already documented in the input schema, which sets the baseline at 3. The description reinforces the meaning of `format` (Markdown documentation vs structured JSON) and the measure scope, but adds no syntax, naming, or disambiguation detail beyond what the schema already states.

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

Purpose4/5

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

The description gives a specific verb (trace) and resource (a DAX measure) and enumerates the exact traversal chain it follows: Dependent Measures -> Model Columns & Tables -> Power Query M Steps -> Upstream Dataflows -> Native SQL & Physical Sources. It also names the two output forms. It does not explicitly differentiate itself from the closest sibling, pbi_measure_lineage, so the agent must infer that the difference is depth/end-to-end coverage rather than simple lineage.

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

Usage Guidelines3/5

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

Usage is implied by the word 'end-to-end' and the deep source chain, suggesting this is the heavyweight full-path trace. But there is no explicit when-to-use, when-not-to-use, or statement of how it differs from pbi_measure_lineage or pbi_source_impact, so selection among overlapping lineage tools is left to inference.

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