Scopewalker MCP

Overview Schema Source Related Servers Discussions Admin

Prop Drilling

get_prop_drilling

Read-onlyIdempotent

Detect prop drilling by finding parameter names passed through chains of functions. Use limit or summary_only to control output.

Instructions

Detects parameter threading (prop drilling) by finding parameter names passed through chains of functions. Use limit/summary_only to control output.

Input Schema

Name	Required	Description
`path`	Yes	File or directory to analyze; must be inside the allowed roots
`limit`	No	Max parameters returned (default 20)
`max_depth`	No	Max directory depth to descend (default unlimited)
`max_files`	No	Stop after scanning this many files (default unlimited)
`extensions`	No	Only scan these extensions, e.g. [".ts", ".py"] (default all supported)
`summary_only`	No	Return summary totals without per-item details (default false)
`exclude_common`	No	Exclude common parameter names like id, key, className (default false)
`include_hidden`	No	Include dotfiles and dot-directories (default false)
`ignore_patterns`	No	Extra gitignore-style patterns to exclude, relative to path
`min_occurrences`	No	Minimum function occurrences to flag (default 3)

Output Schema

Name	Required	Description	Default
`path`	Yes
`_meta`	No
`summary`	Yes
`is_directory`	Yes
`threaded_parameters`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed10 schema fields changedv1.4.0Oct 15, 2026

removedInput schema / additionalProperties
```
Removed value: -false
```

changedInput schema / properties / extensions / description

Previous value: -"Filter by extensions"New value: +"Only scan these extensions, e.g. [\".ts\", \".py\"] (default all supported)"

changedInput schema / properties / ignore_patterns / description

Previous value: -"Exclude patterns"New value: +"Extra gitignore-style patterns to exclude, relative to path"

changedInput schema / properties / include_hidden / description

Previous value: -"Include hidden"New value: +"Include dotfiles and dot-directories (default false)"

changedInput schema / properties / limit / description

Previous value: -"Max results"New value: +"Max parameters returned (default 20)"

changedInput schema / properties / max_depth / description

Previous value: -"Max depth"New value: +"Max directory depth to descend (default unlimited)"

changedInput schema / properties / max_files / description

Previous value: -"Max files to scan"New value: +"Stop after scanning this many files (default unlimited)"

changedInput schema / properties / path / description

Previous value: -"Target path"New value: +"File or directory to analyze; must be inside the allowed roots"

changedInput schema / properties / summary_only / description

Previous value: -"Return only summary without per-parameter details (default false)"New value: +"Return summary totals without per-item details (default false)"

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": false,
+  "properties": {
+    "_meta": {
+      "additionalProperties": false,
+      "properties": {
+        "funding": {
+          "type": "string"
+        },
+        "item_count": {
+          "type": "number"
+        },
+        "response_size_chars": {
+          "type": "number"
+        },
+        "warning": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "item_count",
+        "response_size_chars",
+        "funding"
+      ],
+      "type": "object"
+    },
+    "is_directory": {
+      "type": "boolean"
+    },
+    "path": {
+      "type": "string"
+    },
+    "summary": {
+      "additionalProperties": false,
+      "properties": {
+        "files_analyzed": {
+          "type": "number"
+        },
+        "highest_occurrence": {
+          "anyOf": [
+            {
+              "additionalProperties": false,
+              "properties": {
+                "count": {
+                  "type": "number"
+                },
+                "name": {
+                  "type": "string"
+                }
+              },
+              "required": [
+                "name",
+                "count"
+              ],
+              "type": "object"
+            },
+            {
+              "type": "null"
+            }
+          ]
+        },
+        "threaded_parameters_found": {
+          "type": "number"
+        },
+        "total_parameters_scanned": {
+          "type": "number"
+        }
+      },
+      "required": [
+        "files_analyzed",
+        "total_parameters_scanned",
+        "threaded_parameters_found",
+        "highest_occurrence"
+      ],
+      "type": "object"
+    },
+    "threaded_parameters": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "files": {
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "forwarding_evidence": {
+            "type": "number"
+          },
+          "functions": {
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "name": {
+            "type": "string"
+          },
+          "occurrences": {
+            "type": "number"
+          },
+          "risk": {
+            "enum": [
+              "high",
+              "medium",
+              "low"
+            ],
+            "type": "string"
+          }
+        },
+        "required": [
+          "name",
+          "occurrences",
+          "files",
+          "functions",
+          "forwarding_evidence",
+          "risk"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "path",
+    "is_directory",
+    "threaded_parameters",
+    "summary"
+  ],
+  "type": "object"
+}

Changed9 schema fields changedv1.3.0Sep 15, 2026
- addedInput schema / properties / extensions / items / maxLength
```
Added value: +32
```
- addedInput schema / properties / extensions / items / pattern
```
Added value: +"^\\.?[A-Za-z0-9_+-]+$"
```
- addedInput schema / properties / extensions / maxItems
```
Added value: +100
```
- addedInput schema / properties / ignore_patterns / items / maxLength
```
Added value: +512
```
- addedInput schema / properties / ignore_patterns / maxItems
```
Added value: +100
```
- changedInput schema / properties / limit / maximum
```
Previous value: -9007199254740991New value: +5000
```
- changedInput schema / properties / max_depth / maximum
```
Previous value: -9007199254740991New value: +64
```
- changedInput schema / properties / max_files / maximum
```
Previous value: -9007199254740991New value: +10000
```
- changedInput schema / properties / min_occurrences / maximum
```
Previous value: -9007199254740991New value: +1000
```
First observedv1.0.4Jul 31, 2026

TDQS

B3.2/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered and the description need not restate it. It adds the analysis semantics (chains of functions, parameter names) but nothing about scope of scanning, cost, or what the findings look like. Adequate but thin for a static-analysis tool.

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?

Two short sentences, front-loaded with the definition and followed by a brief output-control hint. Nothing is padded, though the second sentence largely echoes schema defaults rather than earning much new information.

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?

Safety is covered by annotations, return shape by the output schema, and all 10 parameters by a fully documented schema, so the structural gaps are small. The remaining hole is usage framing: an agent learns what the tool detects but not when to reach for it over the other eight code-analysis siblings.

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 description coverage is 100%, covering path, limit, max_depth, max_files, extensions, summary_only, exclude_common, include_hidden, ignore_patterns, and min_occurrences with defaults and bounds. The description mentions only limit and summary_only and adds no syntax, default, or interaction detail beyond the schema, so the baseline 3 applies.

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?

States a specific detection target (parameter threading / prop drilling) and the mechanism (parameter names passed through chains of functions), which separates it from siblings like get_code_smells or get_complexity_metrics. It stops short of naming any sibling explicitly, so differentiation is conceptual rather than direct.

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

Usage Guidelines2/5

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

The only guidance is 'Use limit/summary_only to control output', which is a parameter hint rather than a when-to-use rule. It never says when this analysis is preferable to get_code_smells or get_functions, nor any prerequisite or exclusion conditions.

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

Deploy Server