Skip to main content
Glama

pbi_measure_lineage

Trace full upstream and downstream lineage for a DAX measure, showing referenced columns, base measures, dependent KPIs, and reports to assess change impact.

Instructions

Return full upstream (referenced columns and base measures) and downstream (dependent KPIs and reports) lineage for a DAX measure.

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_measure_lineage"
  }
}

Input Schema

NameRequiredDescriptionDefault
modelNoOptional semantic model name filter.
measureYesDAX measure name.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

No annotations exist, so the description carries the full burden. It usefully enumerates the categories returned (referenced columns, base measures, dependent KPIs, reports) but says nothing about read-only semantics, permissions, depth limits, size limits on large models, or pagination.

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?

A single front-loaded sentence with zero filler, using parentheticals to define both directions of lineage efficiently. Slightly dense but nothing that could be cut without losing information.

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 simple two-parameter read tool with no output schema, the description does the key work of telling the agent what categories of entities come back. It is thin on return structure and on the model-filter/measure ambiguity, but nothing critical is missing for a correct invocation.

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 both parameters are already documented. The description adds no syntax or matching guidance beyond 'for a DAX measure' — it does not say whether the measure name must be unique across models or how the model filter interacts with it, which matters given ambiguous measure names.

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?

Names a specific verb ('Return'), a specific resource ('lineage'), and scopes it to a DAX measure, with parenthetical detail on what upstream and downstream mean. Clear enough that an agent can distinguish it from pbi_inspect_model or pbi_health_audit, though it never names a sibling explicitly.

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 only implied: the mention of 'upstream' and 'downstream' signals this is for impact/dependency analysis. There is no explicit when-to-use, no when-not-to-use, and no pointer to an alternative such as pbi_source_impact for data-source-level impact.

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