# Impact analysis, defined with a sourced example

GLOSSARY, read 10 Nov 2026

**The short answer.** The question of what breaks downstream if an asset changes or fails. An agent answers it by walking dependencies from the asset to the dashboards, models and reports that read from it. Per Sifflet's README, the server can start from an incident and trace the downstream assets affected, and its get_downstream_assets_of_asset tool returns them by URN.

## Definition

The question of what breaks downstream if an asset changes or fails. An agent answers it by walking dependencies from the asset to the dashboards, models and reports that read from it.

## Example from a real server

**Example.** Per Sifflet's README, the server can start from an incident and trace the downstream assets affected, and its get_downstream_assets_of_asset tool returns them by URN.

## Related terms

- [input schema](/glossary/input-schema/): A JSON Schema that states which arguments a tool accepts, their types and which are required or limited to set values.
- [local MCP server](/glossary/local-mcp-server/): An MCP server that runs on the engineer's own machine or infrastructure, usually started by the client over stdio.
- [human confirmation](/glossary/human-confirmation/): A step where a person approves a tool call before it runs.

## Where to read more

- [The directory](/)
- [All glossary terms](/glossary/)

## Sources

- github.com/siffletdata/sifflet-mcp/blob/main/README.md: https://github.com/siffletdata/sifflet-mcp/blob/main/README.md (read 10 Nov 2026)

Last reviewed 10 Nov 2026. Canonical: https://datamcpservers.com/glossary/impact-analysis/
