Scopewalker MCP

Overview Schema Source Related Servers Discussions Admin

Code Inventory

get_code_inventory

Read-onlyIdempotent

Lists classes, functions, methods, and exports within a file or directory, allowing extension filters to inventory symbols across a codebase.

Instructions

Lists classes, functions, methods, and exports. Use extensions to filter.

Input Schema

Name	Required	Description
`grep`	No	Keep files or symbols whose path or name contains this text (case-insensitive)
`path`	Yes	File or directory to analyze; must be inside the allowed roots
`limit`	No	Max files 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)
`include_hidden`	No	Include dotfiles and dot-directories (default false)
`ignore_patterns`	No	Extra gitignore-style patterns to exclude, relative to path
`include_private`	No	Include private and unexported symbols (default false)

Output Schema

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

Previous value: -"Filter by keyword"New value: +"Keep files or symbols whose path or name contains this text (case-insensitive)"

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

Previous value: -"Include private symbols"New value: +"Include private and unexported symbols (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"

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"
+    },
+    "inventory": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "file": {
+            "type": "string"
+          },
+          "items": {
+            "items": {
+              "additionalProperties": false,
+              "properties": {
+                "exported": {
+                  "type": "boolean"
+                },
+                "line": {
+                  "type": "number"
+                },
+                "methods": {
+                  "items": {
+                    "additionalProperties": false,
+                    "properties": {
+                      "line": {
+                        "type": "number"
+                      },
+                      "name": {
+                        "type": "string"
+                      },
+                      "visibility": {
+                        "enum": [
+                          "public",
+                          "private",
+                          "protected"
+                        ],
+                        "type": "string"
+                      }
+                    },
+                    "required": [
+                      "name",
+                      "line",
+                      "visibility"
+                    ],
+                    "type": "object"
+                  },
+                  "type": "array"
+                },
+                "name": {
+                  "type": "string"
+                },
+                "type": {
+                  "enum": [
+                    "class",
+                    "function",
+                    "interface",
+                    "enum",
+                    "constant"
+                  ],
+                  "type": "string"
+                }
+              },
+              "required": [
+                "name",
+                "type",
+                "line",
+                "exported"
+              ],
+              "type": "object"
+            },
+            "type": "array"
+          }
+        },
+        "required": [
+          "file",
+          "items"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "path": {
+      "type": "string"
+    },
+    "summary": {
+      "additionalProperties": false,
+      "properties": {
+        "exported_symbols": {
+          "type": "number"
+        },
+        "total_classes": {
+          "type": "number"
+        },
+        "total_files": {
+          "type": "number"
+        },
+        "total_functions": {
+          "type": "number"
+        },
+        "total_methods": {
+          "type": "number"
+        }
+      },
+      "required": [
+        "total_files",
+        "total_classes",
+        "total_functions",
+        "total_methods",
+        "exported_symbols"
+      ],
+      "type": "object"
+    }
+  },
+  "required": [
+    "path",
+    "inventory",
+    "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
```

Changed1 schema field changedv1.0.5Aug 2, 2026

removedInput schema / properties / group_by

Removed value: -{
-  "description": "Grouping method",
-  "enum": [
-    "file",
-    "type",
-    "directory"
-  ],
-  "type": "string"
-}

First observedv1.0.4Jul 31, 2026

TDQS

C2.9/5.0

Behavior2/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 fully covered elsewhere. The description adds no behavioral context of its own: no scan/recursion behavior, no note about default limits or hidden-file handling, and no output shape beyond the resource list.

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 with the core purpose front-loaded and no filler. The second sentence is largely duplicative of the extensions schema description, keeping it just below a 5.

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 no explanation, and the schema documents every parameter. However, for a 9-parameter scanning tool sitting among closely related siblings, the description omits the guidance needed to pick it correctly and says nothing about scanning defaults or scope limits.

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% across all nine parameters, including the extensions filter the description mentions, so the schema already does the heavy lifting. The one sentence about extensions is redundant with the structured field rather than additive, which lands this at the baseline 3.

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 gives a concrete verb ('Lists') plus the resource set (classes, functions, methods, exports), so an agent immediately knows what comes back. It does not distinguish itself from the sibling get_functions, which the same agent may also consider, so it stops short of a 5.

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 extensions to filter,' which is a parameter tip rather than a when-to-use rule. Nothing says when this tool is preferable to get_functions or the other inventory-style siblings, and no prerequisites or exclusions are stated.

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

Deploy Server