Skip to main content
Glama
timohaa

Scopewalker MCP

by timohaa
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

get_code_inventory

List classes, functions, methods, and exports in a codebase with filters for extensions, keywords, depth, and file limits.

Instructions

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
grepNoFilter by keyword
pathYesTarget path
limitNoMax results
max_depthNoMax depth
max_filesNoMax files to scan
extensionsNoFilter by extensions
include_hiddenNoInclude hidden
ignore_patternsNoExclude patterns
include_privateNoInclude private symbols

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changedv1.3.0
    • 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
  2. Changed1 schema field changedv1.0.5
    • removedInput schema / properties / group_by
      Removed value: -{
-  "description": "Grouping method",
-  "enum": [
-    "file",
-    "type",
-    "directory"
-  ],
-  "type": "string"
-}
  3. First observedv1.0.4

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. 'Lists' implies a read-only operation, but the description does not state whether the operation is safe, how it handles large codebases, or what the response structure is. It also does not disclose potential performance implications or the meaning of 'extensions' beyond a vague filter hint.

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?

The description is two short sentences, front-loading the primary action and then giving a filtering hint. It is concise with no filler. However, it could be slightly more structured to include usage context, but as-is it is efficient.

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

Completeness2/5

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

With 9 parameters, no output schema, and no annotations, the description is insufficiently complete. It does not explain what the output looks like, how results are ordered, or any default behaviors. It also does not provide guidance on when to use this vs. more specific tools like get_functions, leaving an agent to infer the tool's role. This is a significant gap for a complex inventory tool.

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 parameters already have descriptions. The tool description adds only a minor hint about using extensions to filter, which slightly reinforces the extension parameter but does not add substantive meaning beyond the schema. The baseline of 3 is appropriate because the schema handles parameter semantics fully.

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 states a specific verb 'lists' and identifies the resource as classes, functions, methods, and exports. It clearly indicates the tool produces an inventory of code symbols. However, it does not explicitly distinguish from siblings like get_functions, which might lead to ambiguity, but the broad scope is reasonably clear.

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 description only says 'Use extensions to filter,' which is a usage hint for filtering but not guidance on when to choose this tool over alternatives. It does not mention when not to use it or compare to siblings like get_functions or get_code_smells. No context about the appropriate scenario is provided.

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

Deploy Server

Other Tools