Scopewalker MCP

Overview Schema Source Related Servers Discussions Admin

Code Smells

get_code_smells

Read-onlyIdempotent

Detect TODO, FIXME, HACK, BUG, deprecated, unused, and unsafe casts in source files or directories to surface code quality issues before review.

Instructions

Finds TODO/FIXME/HACK/BUG markers and unsafe casts in code.

Input Schema

Name	Required	Description
`path`	Yes	File or directory to analyze; must be inside the allowed roots
`limit`	No	Max files returned (default 20)
`types`	No	Smell types to detect (default all)
`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_text`	No	Include each marker's comment text (default false)
`include_hidden`	No	Include dotfiles and dot-directories (default false)
`ignore_patterns`	No	Extra gitignore-style patterns to exclude, relative to path

Output Schema

Name	Required	Description	Default
`path`	Yes
`_meta`	No
`files`	Yes
`summary`	Yes
`is_directory`	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 / include_text / description

Previous value: -"Include comment text"New value: +"Include each marker's comment text (default false)"

changedInput schema / properties / limit / description

Previous value: -"Max results"New value: +"Max files 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 / types / description

Previous value: -"Smell types to detect"New value: +"Smell types to detect (default all)"

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"
+    },
+    "files": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "path": {
+            "type": "string"
+          },
+          "smells": {
+            "items": {
+              "additionalProperties": false,
+              "properties": {
+                "line": {
+                  "type": "number"
+                },
+                "path": {
+                  "type": "string"
+                },
+                "text": {
+                  "type": "string"
+                },
+                "type": {
+                  "enum": [
+                    "todo",
+                    "fixme",
+                    "hack",
+                    "xxx",
+                    "bug",
+                    "unused",
+                    "deprecated",
+                    "unsafe_cast"
+                  ],
+                  "type": "string"
+                }
+              },
+              "required": [
+                "path",
+                "line",
+                "type",
+                "text"
+              ],
+              "type": "object"
+            },
+            "type": "array"
+          }
+        },
+        "required": [
+          "path",
+          "smells"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "is_directory": {
+      "type": "boolean"
+    },
+    "path": {
+      "type": "string"
+    },
+    "summary": {
+      "additionalProperties": false,
+      "properties": {
+        "by_type": {
+          "additionalProperties": {
+            "type": "number"
+          },
+          "propertyNames": {
+            "enum": [
+              "todo",
+              "fixme",
+              "hack",
+              "xxx",
+              "bug",
+              "unused",
+              "deprecated",
+              "unsafe_cast"
+            ],
+            "type": "string"
+          },
+          "required": [
+            "todo",
+            "fixme",
+            "hack",
+            "xxx",
+            "bug",
+            "unused",
+            "deprecated",
+            "unsafe_cast"
+          ],
+          "type": "object"
+        },
+        "files_with_smells": {
+          "type": "number"
+        },
+        "total_files_scanned": {
+          "type": "number"
+        },
+        "total_smells": {
+          "type": "number"
+        }
+      },
+      "required": [
+        "total_files_scanned",
+        "files_with_smells",
+        "total_smells",
+        "by_type"
+      ],
+      "type": "object"
+    }
+  },
+  "required": [
+    "path",
+    "is_directory",
+    "files",
+    "summary"
+  ],
+  "type": "object"
+}

Changed8 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
```
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=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is clear. The description adds that it finds specific marker types and unsafe casts, which is useful content context. It does not add behavioral details beyond the schema and annotations, such as default hidden-file handling or output shape, but with annotations covering the safety profile a 3 is appropriate.

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 front-loaded sentence with zero filler. It states the core purpose immediately without unnecessary elaboration.

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?

The tool has nine parameters, an output schema, and rich annotations, so the description need not explain returns or safety. However, for a scanning tool with several siblings, the description is thin on usage context and does not help an agent choose between this and find_dead_code or get_code_inventory. It is minimally adequate but leaves clear selection gaps.

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%, so all nine parameters are fully documented in the schema. The description mentions only a subset of the detectable types (TODO/FIXME/HACK/BUG and unsafe casts), adding no syntax or format details beyond what the schema provides. Baseline 3 applies when the schema does the heavy lifting.

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?

The description uses a specific verb ('Finds') and names the target artifacts: TODO/FIXME/HACK/BUG markers and unsafe casts. This distinguishes it from many siblings such as get_line_counts or get_complexity_metrics. However, it does not explicitly differentiate from the closest sibling, find_dead_code, leaving a small ambiguity.

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?

There is no guidance on when to use this tool versus alternatives. Sibling tools like find_dead_code and get_code_inventory overlap in static analysis scope, but the description offers no conditions, exclusions, or routing advice.

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

Deploy Server