lineage-impact
Analyze downstream impact of metadata changes by walking lineage, counting affected consumers, and identifying top dependent entities and owners.
Instructions
Aggregated downstream impact analysis: walks lineage (default 3 levels down, 1 up), counts unique consumers, breaks down by entity type, surfaces highest-fan-out top consumers, and (optionally) resolves the union of owners affected. Answers 'who/what breaks if I change X?' in one call instead of recursive get-lineage walks. Renders an Apps SDK card on ChatGPT clients.
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": {
"entity": "<entity>",
"fqn": "<fqn>"
},
"name": "lineage-impact"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| entity | Yes | Entity type | |
| fqn | Yes | Entity fully qualified name (e.g. 'mysql.default.warehouse.orders') | |
| downstreamDepth | No | Lineage depth to walk downstream (default 3, max 5) | |
| upstreamDepth | No | Lineage depth to walk upstream (default 1) | |
| includeOwners | No | Resolve owners (users/teams) of each downstream entity for change-management notifications | |
| topConsumersLimit | No | Number of highest-degree downstream consumers to surface in the summary |