mcp-repo-graph

impact

Read-only

Find everything affected by or depending on specific nodes, ranked by impact, with dead code detection.

Instructions

Blast radius in one call: fan out from one or more nodes to everything they affect (forward) or depend on / are used by (backward), returned as a complete, deduped, Personalized-PageRank-ranked, located closure. Each row carries path:line, the edge via reason it's in scope, and a ⊘ when the engine finds it unreachable from any entry point (likely dead). Structural import/containment fan-out is excluded — no noise. Depth-1 in both directions is a node's immediate neighbours. Pass several comma-separated nodes to assess a whole diff at once.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`depth`	No	How many hops to fan out. Default 4.
`nodes`	Yes	One or more node names/qnames, comma-separated. A diff touching N symbols is one call.
`top_k`	No	Cap the ranked result. 0 = no cap.
`budget`	No	Max chars in the result. 0 = no cap.
`direction`	No	'forward' (what it affects), 'backward' (what it depends on / who uses it), or 'both'. (Aliases: downstream=forward, upstream=backward.)	both
`live_only`	No	Drop nodes not reachable from any entry point (likely-dead code). Default False = show all, marking dead ones ⊘.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed8 schema fields changedv0.4.20Jul 12, 2026

changedInput schema / properties / depth / default
```
Previous value: -3New value: +4
```

changedInput schema / properties / depth / description

Previous value: -"How many hops to traverse. Default 3."New value: +"How many hops to fan out. Default 4."

changedInput schema / properties / direction / default
```
Previous value: -"downstream"New value: +"both"
```

changedInput schema / properties / direction / description

Previous value: -"'downstream' (what it affects) or 'upstream' (what it depends on)."New value: +"'forward' (what it affects), 'backward' (what it depends on / who uses it), or 'both'. (Aliases: downstream=forward, upstream=backward.)"

addedInput schema / properties / live_only

Added value: +{
+  "default": false,
+  "description": "Drop nodes not reachable from any entry point (likely-dead code). Default False = show all, marking dead ones ⊘.",
+  "title": "Live Only",
+  "type": "boolean"
+}

removedInput schema / properties / mode

Removed value: -{
-  "default": "table",
-  "description": "'table' (tiered list) or 'prose' (primed prose for LLM context).",
-  "title": "Mode",
-  "type": "string"
-}

changedInput schema / properties / nodes / description

Previous value: -"One or more node names/qnames, comma-separated. A diff touching N files is one call."New value: +"One or more node names/qnames, comma-separated. A diff touching N symbols is one call."

addedInput schema / properties / top_k

Added value: +{
+  "default": 0,
+  "description": "Cap the ranked result. 0 = no cap.",
+  "maximum": 200,
+  "minimum": 0,
+  "title": "Top K",
+  "type": "integer"
+}

Changed6 schema fields changedv0.4.19Jun 9, 2026

addedInput schema / properties / budget

Added value: +{
+  "default": 0,
+  "description": "Max chars in the result. 0 = no cap.",
+  "minimum": 0,
+  "title": "Budget",
+  "type": "integer"
+}

changedInput schema / properties / direction / description

Previous value: -"'downstream' or 'upstream'."New value: +"'downstream' (what it affects) or 'upstream' (what it depends on)."

addedInput schema / properties / mode

Added value: +{
+  "default": "table",
+  "description": "'table' (tiered list) or 'prose' (primed prose for LLM context).",
+  "title": "Mode",
+  "type": "string"
+}

removedInput schema / properties / node

Removed value: -{
-  "description": "Node name or qname pattern to analyze.",
-  "title": "Node",
-  "type": "string"
-}

addedInput schema / properties / nodes

Added value: +{
+  "description": "One or more node names/qnames, comma-separated. A diff touching N files is one call.",
+  "title": "Nodes",
+  "type": "string"
+}

changedInput schema / required

Previous value: -[
-  "node"
-]New value: +[
+  "nodes"
+]

Changed5 schema fields changedv0.1.3May 2, 2026
- addedInput schema / properties / depth / description
```
Added value: +"How many hops to traverse. Default 3."
```
- addedInput schema / properties / depth / maximum
```
Added value: +10
```
- addedInput schema / properties / depth / minimum
```
Added value: +1
```
- addedInput schema / properties / direction / description
```
Added value: +"'downstream' or 'upstream'."
```
- addedInput schema / properties / node / description
```
Added value: +"Node name or qname pattern to analyze."
```
First observedv0.1.2Apr 13, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Beyond the readOnlyHint annotation, the description reveals key behaviors: ranking algorithm (Personalized PageRank), result fields (path:line, via, dead marker), exclusion of structural edges, depth meaning, and handling of multiple nodes. No contradictions.

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

Conciseness5/5

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

The description is a single dense paragraph that front-loads the core functionality. Every sentence contributes meaningful detail, with no wasted words. It efficiently communicates complex behavior.

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

Completeness5/5

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

Given the tool's complexity and rich parameters/output, the description fully covers result structure, filtering, ranking, and exclusive behavior. It matches the needed detail without relying on output schema.

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

Parameters4/5

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

With 100% schema coverage, the baseline is 3. The description adds value by explaining node usage for whole diffs, aliases for direction, and the meaning of depth-1. This enriches the schema descriptions.

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

Purpose5/5

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

The description clearly states the tool's purpose: computing blast radius/impact from nodes in forward or backward directions. It distinguishes itself from siblings like trace and find by emphasizing its comprehensive, deduped, ranked closure and exclusion of structural edges.

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

Usage Guidelines4/5

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

The description implies when to use this tool (assessing impact of changes, whole diff) and even hints at what it excludes (structural fan-out). However, it doesn't explicitly compare to alternatives or state when not to use it.

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

Deploy Server