Scopewalker MCP

Overview Schema Source Related Servers Discussions Admin

Size Thresholds

check_thresholds

Read-onlyIdempotent

Analyze a file or directory to find files and functions that exceed line-count thresholds. Set limits, depth, or file constraints to control returned violations.

Instructions

Finds files/functions exceeding size thresholds. Use limit to control output.

Input Schema

Name	Required	Description
`path`	Yes	File or directory to analyze; must be inside the allowed roots
`limit`	No	Max violations returned per list (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)
`include_hidden`	No	Include dotfiles and dot-directories (default false)
`max_file_lines`	No	Flag files longer than this many lines (default 300)
`ignore_patterns`	No	Extra gitignore-style patterns to exclude, relative to path
`max_function_lines`	No	Flag functions longer than this many lines (default 100)

Output Schema

Name	Required	Description	Default
`path`	Yes
`_meta`	No
`summary`	Yes
`thresholds`	Yes
`violations`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed11 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 violations"New value: +"Max violations returned per list (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_file_lines / description

Previous value: -"File line threshold"New value: +"Flag files longer than this many lines (default 300)"

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 / max_function_lines / description

Previous value: -"Function line threshold"New value: +"Flag functions longer than this many lines (default 100)"

changedInput schema / properties / path / description

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

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"
+    },
+    "path": {
+      "type": "string"
+    },
+    "summary": {
+      "additionalProperties": false,
+      "properties": {
+        "file_violations": {
+          "type": "number"
+        },
+        "files_checked": {
+          "type": "number"
+        },
+        "files_skipped": {
+          "type": "number"
+        },
+        "function_violations": {
+          "type": "number"
+        },
+        "functions_checked": {
+          "type": "number"
+        },
+        "scan_complete": {
+          "type": "boolean"
+        }
+      },
+      "required": [
+        "files_checked",
+        "functions_checked",
+        "file_violations",
+        "function_violations",
+        "files_skipped",
+        "scan_complete"
+      ],
+      "type": "object"
+    },
+    "thresholds": {
+      "additionalProperties": false,
+      "properties": {
+        "max_file_lines": {
+          "type": "number"
+        },
+        "max_function_lines": {
+          "type": "number"
+        }
+      },
+      "required": [
+        "max_file_lines",
+        "max_function_lines"
+      ],
+      "type": "object"
+    },
+    "violations": {
+      "additionalProperties": false,
+      "properties": {
+        "oversized_files": {
+          "items": {
+            "additionalProperties": false,
+            "properties": {
+              "exceeds_by": {
+                "type": "number"
+              },
+              "lines": {
+                "type": "number"
+              },
+              "path": {
+                "type": "string"
+              }
+            },
+            "required": [
+              "path",
+              "lines",
+              "exceeds_by"
+            ],
+            "type": "object"
+          },
+          "type": "array"
+        },
+        "oversized_functions": {
+          "items": {
+            "additionalProperties": false,
+            "properties": {
+              "exceeds_by": {
+                "type": "number"
+              },
+              "function_name": {
+                "type": "string"
+              },
+              "lines": {
+                "type": "number"
+              },
+              "path": {
+                "type": "string"
+              },
+              "start_line": {
+                "type": "number"
+              }
+            },
+            "required": [
+              "path",
+              "function_name",
+              "lines",
+              "exceeds_by",
+              "start_line"
+            ],
+            "type": "object"
+          },
+          "type": "array"
+        }
+      },
+      "required": [
+        "oversized_files",
+        "oversized_functions"
+      ],
+      "type": "object"
+    }
+  },
+  "required": [
+    "path",
+    "thresholds",
+    "violations",
+    "summary"
+  ],
+  "type": "object"
+}

Changed10 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_file_lines / maximum
```
Previous value: -9007199254740991New value: +10000
```
- changedInput schema / properties / max_files / maximum
```
Previous value: -9007199254740991New value: +10000
```
- changedInput schema / properties / max_function_lines / maximum
```
Previous value: -9007199254740991New value: +10000
```
First observedv1.0.4Jul 31, 2026

TDQS

B3.3/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 safety is well covered. The description adds that it detects violations and that limit controls output size, but does not describe scanning scope defaults or output ordering.

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?

Two short sentences, purpose front-loaded, with no wasted wording. The limit sentence is brief and does not distract from the main purpose.

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?

An output schema exists, so return values need not be explained, and the schema richly documents all parameters. However, with nine parameters and many sibling tools, the description lacks routing guidance about when to choose this tool over alternatives.

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%, with every parameter documented including defaults and bounds. The description only restates 'Use limit to control output,' adding no meaning beyond the schema.

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 verb and resource: finds files/functions exceeding size thresholds. This is clear enough to distinguish from counting tools like get_line_counts, but it does not explicitly name or contrast any sibling tool.

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 to control output,' which is a parameter-level instruction rather than when/when-not to use this tool. There is no mention of alternatives such as get_line_counts or get_complexity_metrics.

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

Deploy Server